Fetch/XHR: test parsing of WWW-Authenticate response header

[annevk]

Context: https://bugzilla.mozilla.org/show_bug.cgi?id=1491010.

[jobisoft]

Have you run this test already? The tests for XHR will probably fail, because XHR returns them "as is"

1\n2\n3,4

[annevk]

Yeah, that's a bug in Firefox. Other browsers don't have that problem.

[jobisoft]

Ok, so the new tests are for after this header stuff has been fixed to match the fetch() API?

I do not want to post this in the bug 1491010, because I do not want to take it off topic. But when you change the behaviour in XHR, can you please expose the "true" header string when getAllResponseHeaders() is called?

From your tests it looks like you want to touch that as well. I think being able to get access to what has actually been send is vital. If the user requests a single header, getting back the comma-joined string is OK, but I should also be able to get the original string.

[annevk]

There's no standard that supports the behavior you want and I don't think it'd be a good idea to special case headers or pass through the server data as-is (as proxies and such could also have meddled with it).

[jobisoft]

Ok, but then you need to get this in the official MDN documentation of XHR as fast as possible, so that coders like me do not rely on the current behaviour.

I was actually thinking about switching from fetch() to XHR because of the current behaviour.