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 23:19 ------- Oleg, I agree, setting a different charset for a single header is not good. If we were to implement this for real I think we would want a config option for all the headers. The only question then would be if we want to allow another different charset for for the username/password before they are digested/base64 encoded. Though using charsets other than ASCII for user names/password does not jibe well with RFC 2616/17, there is no standard solution for handling these cases. Is seems that different vendors have made different choices for supporting non-ASCII values in credentials. To be a good client I think we need to be flexible in how we support authentication. As for 2.0 do you think we should roll back the support for 8859-1 values in basic authentication? Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
