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/06/02 22:29:33 UTC

DO NOT REPLY [Bug 20428] New: - Apache fails to handle extra /'s in the URL line correctly.

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=20428>.
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=20428

Apache fails to handle extra /'s in the URL line correctly.

           Summary: Apache fails to handle extra /'s in the URL line
                    correctly.
           Product: Apache httpd-2.0
           Version: 2.0.46
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: apache@2nd-impact.org


I've recently installed Apache 2.0.46 and noticed that it handles URL
information incorrectly when using a technique called "Clean URLs".  Basically,
a clean url is using a / for a delimiter between variables instead of an & and
reprocessing the data using php or some other scripting engine.  This technique
is useful for 2 things on dynamic websites and previously worked when using
apache 1.x.  Those 2 things are; it allows indexing by search engines (search
engines typically ignore variables) and can also be used for URL obfusication or
simplification.

Since I'm terrible at explaining things, here is an example of a typical URL.
http://servername/index.php?foo=var1&bar=var2

And here is an example of the same URL using the "Clean URL" technique.
http://servername/index.php/var1/var2
or...
http://servername/index.php/foo=var1/bar=var2

The above 2 URLs yeild a 404 error in apache 2.x when it should actually be
executing index.php.  Apache 1.x will execute index.php without a problem.  A
LOT of websites are starting to use this sort of technique or something similar,
and it is the one thing that is keeping me from being able to move to apache 2.x
(it breaks my whole template system).  I've alread made a mention of this on the
PHP bug database and they say it is an Apache bug and is not PHP related.

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