You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2005/11/24 08:55:42 UTC
DO NOT REPLY [Bug 37619] New: -
Please consider LocationMatchExcept
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37619>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37619
Summary: Please consider LocationMatchExcept
Product: Apache httpd-2.0
Version: 2.0.54
Platform: Other
OS/Version: other
Status: NEW
Severity: enhancement
Priority: P2
Component: Core
AssignedTo: bugs@httpd.apache.org
ReportedBy: joerg@dorchain.net
I found myself in a situation where I wanted to apply settings to all except a
certain URL. I found no real workaround but to list each and every location,
having to note that future expansions also needs setting instead of inheriting
defaults. While it is possible to negate a regex, this reads ugly.
LocationMatchExcept would be a friendly alternative. E.g. <LocationMatchExcept
^/not-this> instead of <LocationMatch
^/(([^n]|n[^o]|no[^t]|not[^-]|...|not-thi[^s]).+|.{1,8}$)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org