Robert Sayre wrote:
Some implementations respect the charset
parameter specified in SASL Digest (RFC 2831). Others use the encoding
of the page. No one is quite sure what IE does.
From Microsoft's SSP docs [1]:
"Digest SSP uses the charset directive for both HTTP and SASL mode. This
directive allows the use of UTF-8 in HTTP mode. To maintain backwards
compatibility with clients that do not understand the charset directive, the
realm in the challenge is encoded in the standard ISO 8859-1 (Latin-1)
character set. If the client understands the charset directive, then the
username and realm (and password) can be encoded in UTF-8 in the challenge
response sent back to the server. If the client does not understand the
charset directive, then the standard ISO 8859-1 (Latin-1) must be used."
I would have thought this applied to IE as well as IIS, but reading Gordon's
post it looks like the .NET implementation might be borked. If anyone really
cares it's probably not too much effort to put together a few tests.
Regards
James
[1]
http://technet2.microsoft.com/WindowsServer/en/Library/717b450c-f4a0-4cc9-86f4-cc0633aae5f91033.mspx?mfr=true
