Improved site access matching

Next topic

Author	Message
Jan Borsodi	Wednesday 29 October 2003 2:20:00 am Currently the site access matching system is more complex than it needs to be, for instance it consists of too many separate settings. Also the PHP code that does the matching is hard to read and has already had several bugs (It's better in 3.2-3 and 3.3 thanks to Volker Lenz) I propose to create a totally new matching system which will solve this problems as well as make the system more flexible. 1. The matching Instead of having 5-10 settings for determing how to match I propose a simple list/array of matching rules. Each rule will try to match and if it does returns a site access name, that name is checked against valid site accesses. If the site access is valid it used if not the next rule is checked. a) host SiteAccessMatch[]=hostmap:www.example.com=user SiteAccessMatch[]=hostmap:admin.example.com=admin This has two rules which matches against a hostname an designates it a site access. SiteAccessMatch[]=hostelement:3 Fetches the text from the third element in the hostname and uses it as the site access. eg. www.example.com, here the first element is com and the third is www. SiteAccessMatch[]=hostregexp:(.+).www.example.com:1 Matches the hostname against a regexp and returns the nth submatch, in this case 1. b) port SiteAccessMatch[]=portmap:81=admin Maps a port number to a siteaccess. c) path This was currently known as URI but is really just the path element. SiteAccessMatch[]=pathelement:1 Fetches the nth element of the path (separated by /) and uses that as siteaccess name. SiteAccessMatch[]=pathregexp:^([^/]+)/:1 Matches the path against a regexp and returns the nth element. d) url SiteAccessMatch[]=urlmap:http://www.example.com=user SiteAccessMatch[]=urlmap:https://www.example.com=admin Maps against the whole request url and maps it to a site access. SiteAccessMatch[]=urlregexp:https?://([^.]+).example.com:1 Matches the url against a regexp and uses the nth match as the site access. 2. Compatability The old code should be moved to a new file and a new setting in site.ini should be added. That way it's possible to call the old code if you don't want to change your existing settings. Also all new settings should be placed in a new .ini (e.g. access.ini) file. -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq

Author

Message

Wednesday 29 October 2003 2:20:00 am

Currently the site access matching system is more complex than it needs to be, for instance it consists of too many separate settings.
Also the PHP code that does the matching is hard to read and has already had several bugs (It's better in 3.2-3 and 3.3 thanks to Volker Lenz)

I propose to create a totally new matching system which will solve this problems as well as make the system more flexible.

1. The matching
Instead of having 5-10 settings for determing how to match I propose a simple list/array of matching rules.
Each rule will try to match and if it does returns a site access name, that name is checked against valid site accesses.
If the site access is valid it used if not the next rule is checked.

a) host

SiteAccessMatch[]=hostmap:www.example.com=user
SiteAccessMatch[]=hostmap:admin.example.com=admin

This has two rules which matches against a hostname an designates it a site access.

SiteAccessMatch[]=hostelement:3

Fetches the text from the third element in the hostname and uses it as the site access. eg. www.example.com, here the first element is com and the third is www.

SiteAccessMatch[]=hostregexp:(.+).www.example.com:1

Matches the hostname against a regexp and returns the nth submatch, in this case 1.

b) port

SiteAccessMatch[]=portmap:81=admin

Maps a port number to a siteaccess.

c) path
This was currently known as URI but is really just the path element.

SiteAccessMatch[]=pathelement:1

Fetches the nth element of the path (separated by /) and uses that as siteaccess name.

SiteAccessMatch[]=pathregexp:^([^/]+)/:1

Matches the path against a regexp and returns the nth element.

d) url

SiteAccessMatch[]=urlmap:http://www.example.com=user
SiteAccessMatch[]=urlmap:https://www.example.com=admin

Maps against the whole request url and maps it to a site access.

SiteAccessMatch[]=urlregexp:https?://([^.]+).example.com:1

Matches the url against a regexp and uses the nth match as the site access.

2. Compatability

The old code should be moved to a new file and a new setting in site.ini should be added.
That way it's possible to call the old code if you don't want to change your existing settings.

Also all new settings should be placed in a new .ini (e.g. access.ini) file.

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

eZ debug

Timing:	Jan 18 2025 15:09:29
Script start
Timing:	Jan 18 2025 15:09:29
Module start 'layout'
Timing:	Jan 18 2025 15:09:29
Module start 'content'
Timing:	Jan 18 2025 15:09:30
Module end 'content'
Timing:	Jan 18 2025 15:09:30
Script end

Main resources:

Total runtime	0.6073 sec
Peak memory usage	4,096.0000 KB
Database Queries	46

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	589.3438	152.6250
Module start 'layout'	0.0054	0.0036	741.9688	39.4453
Module start 'content'	0.0090	0.5966	781.4141	475.8906
Module end 'content'	0.6057	0.0016	1,257.3047	8.1641
Script end	0.6073		1,265.4688

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0032	0.5269	16	0.0002
Check MTime	0.0013	0.2216	16	0.0001
Mysql Total
Database connection	0.0008	0.1381	1	0.0008
Mysqli_queries	0.5592	92.0825	46	0.0122
Looping result	0.0004	0.0724	44	0.0000
Template Total	0.5775	95.1	2	0.2887
Template load	0.0019	0.3123	2	0.0009
Template processing	0.5756	94.7718	2	0.2878
Template load and register function	0.0001	0.0168	1	0.0001
states
state_id_array	0.0009	0.1520	1	0.0009
state_identifier_array	0.0010	0.1675	2	0.0005
Override
Cache load	0.0016	0.2576	38	0.0000
Sytem overhead
Fetch class attribute can translate value	0.0007	0.1092	1	0.0007
Fetch class attribute name	0.0006	0.1054	2	0.0003
XML
Image XML parsing	0.0005	0.0802	1	0.0005
class_abstraction
Instantiating content class attribute	0.0000	0.0006	2	0.0000
General
dbfile	0.0006	0.1056	17	0.0000
String conversion	0.0000	0.0015	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
1	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
1	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
6	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
6	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 16 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs