On Apr 25, 7:39 pm, Mfenetre <[EMAIL PROTECTED]> wrote: > I encountered today an unexpected behaviour of Firefox today. When I > receive this kind of http Digest challenge :
from what server/url? > HTTP/1.1 401 Unauthorized > [...] > WWW-Authenticate: Digest realm="X.X.X.X", > nonce="jDtaVwL2Yn41zxAefxOtRZ6FoLB2bAAAAAAAAAAAAAA=", qop="auth-int", > algorithm=AKAv1-MD5 > > Firefox hangs and does not respond to the challenge correctly. when you say hangs, does this mean that you can not use the ui at all? > I don't > see the usual pop-up asking for a username/password when it receives a > Http Digest challenge, and apparently the usual code handling Http > Digest challenge in Firefox is not called (XPCOM component > "@mozilla.org/network/http-authenticator;1?scheme=digest"). > > Firefox works fine with other Http Digest challenge, so I suspect > (since it's the only visible difference) that's because of the > parameter algorithm=AKAv1-MD5. So I've investigated to see how RFC3310 > (dealing with Http Digest AKA) was supposed to be handled by browsers. > > I didn't find any clue about Firefox supposed behaviour when receiving > such a Digest challenge... Could anyone give me any lead/clue/ > information please ? i loaded: http://mxr.mozilla.org/seamonkey/source/netwerk/ and typed 'algorithm' into the search box and pressed search The logical match from the output was: # line 635 -- nsCRT::strncasecmp(challenge+nameStart, "algorithm", 9) == 0) But I personally settled on giving you this link: http://mxr.mozilla.org/seamonkey/source/netwerk/protocol/http/src/nsHttpDigestAuth.cpp#638 feel free to trace the code, but i believe you'll find that we just plain don't support that algorithm. find/file a bug. _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
