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 2003/07/30 18:52:38 UTC

DO NOT REPLY [Bug 21828] - mod_rewrite RewriteCond -U always true

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21828>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21828

mod_rewrite RewriteCond -U always true

nd@perlig.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID



------- Additional Comments From nd@perlig.de  2003-07-30 16:52 -------
>From the mod_rewrite documentation:
===<8====
Checks if TestString is a valid URL and accessible via all the server's
currently-configured access controls for that path.
===8<====

Well, if you protect an URL using auth or host based mechanisms, -U will fail.
Simple test:

Redirect 403 /foo

RewriteCond /foo -U
...

In other words, it does NOT test, whether the URL is catched and successfully
delivered by a handler (if it wanted to, it actually had to run the handler,
which is not desirable and would be nearly impossible to handle). It just tests,
whether the handler can be executed or not.

However, a mod_rewrite-documentation overhaul is planned and a better
explanation of these issues will probably happen then.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org