DO NOT REPLY [Bug 42860] - URI path segment parameters (semicolon-delimited) are not parsed

[bu...@apache.org]

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


slive@apache.org changed:

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




------- Additional Comments From slive@apache.org  2007-07-18 11:14 -------
Neither RFC 2396 nor RFC 2616 say anything about how path_segments should be
mapped to a filesystem. I don't see any requirement that parameters be stripped
by the HTTP server. And you certainly can't add random parameters into the URL
and expect it to map to the same resource.

You seem to be suggesting that the core handler ignore any parameter like it
ignores any query string. I don't see any particular reason to do that. And in
fact, there is not reason to do it with the query string either. Apache would be
just as correct if it rejected with a 404 any request to a static file with a
query string tacked on.

Of course, I'm not a protocol expert, so feel free to reopen if you can show why
apache is required to strip parameters.

-- 
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