Forums / Install & configuration / SiteAccessRules -- how to declare a default access rule for nonmatching requests ?

"Please Note:

At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

SiteAccessRules -- how to declare a default access rule for nonmatching requests ?

Previous topic

Install & configuration

Next topic

Author	Message
Volker Lenz	Sunday 26 January 2003 8:20:29 am Is it possible to declare a default site access rule in ezp3 site.ini or elsewhere to cope with URIs that do not match any of the required patterns like "admin" or "user" in order to decide which access path to follow? I could not find an answer in the docs. What I mean is just e.g. appending something like "StaticMatch" to your Match Order in site.ini to generate a fallback access rule if all other matches fail, say MatchOrder host;uri;static StaticMatch=public Or is this goal perhaps achievable with other config-settings I am just to silly to recognize? What does ezp3 actually do if all matches suggested fail? Any ideas ?

Author

Message

Volker Lenz

Sunday 26 January 2003 8:20:29 am

Is it possible to declare a default site access rule in ezp3 site.ini or elsewhere to cope with URIs that do not match any of the required patterns like "admin" or "user" in order to decide which access path to follow? I could not find an answer in the docs.

What I mean is just e.g. appending something like "StaticMatch" to your Match Order in site.ini to generate a fallback access rule if all other matches fail, say

MatchOrder host;uri;static
StaticMatch=public

Or is this goal perhaps achievable with other config-settings I am just to silly to recognize?

What does ezp3 actually do if all matches suggested fail?

Any ideas ?