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=24333>. 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=24333 Error 403 - when URL with a german umlaut is used [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ErrorMessage, RFC ------- Additional Comments From [EMAIL PROTECTED] 2003-11-07 12:08 ------- I searched RFCs for using national characters in URLs like ä,ö,ü and if it's allowed to encode them in an http url. I found that there could be a problem in Apache2 regarding RFC specification - but I did not found anything about national encoded characters "can" or "must not" be used in http URLs. RFC2396 [7] 2.1 Summary: Special Characters that are not represented in the octet for the US-ASCII code require some way of identifying the charset used. Part of the referenced RFC2277 [2] 3.1: "All protocols MUST identify, for all character data, which charset is in use." Even if there is no problem regarding RFC specification, the error message is misleading. %E4.html - access denied -> wrong message %E4.html - not found -> could be the correct message if national characters are not allowed. "access denied" also occurs if ä.html does not exist. Compared with Apache1: Apache1 is able to send %E4.html back to the browser. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
