Firefox doesn't support userhash in Digest Auth from rfc7616
Categories
(Core :: Networking: HTTP, enhancement, P3)
Tracking
()
People
(Reporter: dveditz, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
The RFC 7616 update to Digest Auth specifies Username Hashing and a userhash parameter in http auth request/response headers which Firefox does not support. Because our responses to a userhash=true request don't respond in kind servers can tell that we don't support it and presumably handle it fine, although the specification gives them the option to reject the request.
This is almost certainly low priority without a compelling usecase, but it was noted by Junior in bug 41489 comment 195 as unfinished work so I'm moving it here in order to close that otherwise long-fixed bug.
|
||
Updated•4 years ago
|
|
|
||
Updated•4 years ago
|
|
||
Comment 1•5 months ago
|
||
Quick note that userhash will be useful for HTTPS proxying, where the username does not travel over the network as clear text.
Obscuring the username when using HTTPS proxies is the key use case for userhash.
Description
•