other/6159: read the full description!

[Jonas J�rgensen <tb...@email.dk>]

>Number:         6159
>Category:       other
>Synopsis:       read the full description!
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          mistaken
>Submitter-Id:   apache
>Arrival-Date:   Wed Jun 07 11:30:29 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator:     tbw@email.dk
>Release:        read the full description!
>Organization:
apache
>Environment:
read the full description!
>Description:
This is NOT a bug report - just a suggestion of a new feature! I KNOW that i'm sending this to the wrong place, but there was no other "contact us" link, os what should i do?!?

Anyway, here goes: How about making Apache servers ignore case when processing a HTTP-request? It would be much better, so you wouldn't have problems with uppercase/lowercase in URLs. And since there anyway can't be two identical filenames just with different case, there is actually no good reason not to make it case-insensitive!

For more information, read http://www.useit.com/alertbox/990321.html
>How-To-Repeat:
read the full description!
>Fix:
read the full description!
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]