On Nov 22, 2003, at 6:31 PM, [EMAIL PROTECTED] wrote:
------- Additional Comments From [EMAIL PROTECTED] 2003-11-22 23:31 -------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.
I think that should go without saying
Yes, the only caveat being that the digest username and the headers will need to be in the same encoding.
As for 2.0 do you think we should roll back the support for 8859-1 values in
basic authentication?
What if we used ISO-8859-1 to encode the password in the digest scheme instead?
We can support 8859-1 in the password, just not the username, since that would require sending the headers as 8859-1. I guess we might as well have partial support for non-ASCII chars now and we can build upon it in 2.1.
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
