Open Bug 1735854 Opened 3 years ago Updated 3 years ago

Support charset parameter in WWW-Authenticate headers

Categories

(Core :: Networking: HTTP, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: dveditz, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Spinning off from bug 41489 comment 195: Firefox does not support the charset parameter added to HTTP Auth in the 2015 rfc7616/7617 updates to the old rfc 2617 we implemented at the time bug 41489 was filed.

The only valid value is "UTF-8" (matched case insensitively) which is what we respond with anyway, and responses don't echo the charset parameter back to the server. There's not much actually involved in supporting this. rfc7617 calls it "purely advisory" and the only thing we could do is:

If the user agent does not support the encoding indicated by the server, it can fail the request.

... which is probably not worth the effort at this time.

See Also: → 41489
See Also: → 656503
Assignee: nobody → valentin.gosu
Severity: -- → S3
Priority: -- → P3
Whiteboard: [necko-triaged]
Assignee: valentin.gosu → nobody
Blocks: necko-auth
You need to log in before you can comment on or make changes to this bug.