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=24671>. 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=24671 Basic Authentification fails with non-ASCII username/password characters ------- Additional Comments From [EMAIL PROTECTED] 2003-11-22 22:42 ------- Mike, I do not like the idea of using non-ASCII characters in 'Authorization' headers, at least in those headers only. Probably we should introduce an option to encode HTTP headers using ISO-8859-1 or UTF-8 to accommodate for all sorts of not-so-compliant behaviors with regards to HTTP header content. This said, I do think that digest scheme user names are not meant to have non-ASCII content, as it would constitute a gross violation of the RFC2616. But I do admit that it can be subject to different interpretations I am +1 to stick to ASCII for the 2.0 release, as least for user names Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
