FYI: I observed this with Thunderbird 60.3.1 (the current stable release)
Is this related to
https://bugzilla.mozilla.org/show_bug.cgi?id=1491010
I reported this bug because fetch()'s response.headers.get("WWW-Authenticate")
returned "null" if TWO such headers are received (as you suggested).
In the course of that bug, they discussed how to return such headers and
decided to flatten them and return them as a list separated by ", ". This is
according to the specs.
Furthermore they realized, that XHR currently is NOT flattening such multiple
WWW-Authenticate headers, but returns them as a list separated by "\n". They
decided to change that. This forces all XHR users to manually split
WWW-Authenticate headers (which is complicated, as you pointed out). But it is
according to the specs, so we have to live with that.
Now it looks like that nsIHttpChannel itself is not able to split
WWW-Authenticate headers?
Should I add a link to this thread to the existing bug?
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
