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 2008/02/24 22:48:15 UTC
DO NOT REPLY [Bug 44477] - Apache accepts lowercase input
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<https://issues.apache.org/bugzilla/show_bug.cgi?id=44477>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
https://issues.apache.org/bugzilla/show_bug.cgi?id=44477
slive@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution| |INVALID
Status|NEW |RESOLVED
------- Additional Comments From slive@apache.org 2008-02-24 13:48 -------
What standard exactly is being violated here?
Some of your assumptions are wrong. When apache sees "get /foo" it treats it
exactly like "BAR /foo". In other words, it treats it as an unknown method
acting on an improperly-canonicalized directory. It is not doing a
case-insensitive match on GET.
So what is happening is that apache ignores the method entirely when it receives
a request for an improperly-canonicalized directory and simply sends the
redirect. In the case of "BAR /foo", apache doesn't even try to determine
whether the resource /foo will actually deal with the method BAR. Trying to
check this would add considerable complexity for very little gain.
And by the way, "get /foo" and even "GET /foo/" are not correct requests in any
recent version of http. If you are testing protocol compliance, you should start
with a reasonable request.
--
Configure bugmail: https://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