Re: [whatwg/xhr] setRequestHeader behavior doesn't seem to match implementations (#108) from Anne van Kesteren on 2017-01-27 (public-webapps-github@w3.org from January 2017)

From: Anne van Kesteren <notifications@github.com>
Date: Fri, 27 Jan 2017 08:25:22 -0800
To: whatwg/xhr <xhr@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/xhr/issues/108/275707105@github.com>

So I created this response to test `getAllResponseHeaders()` and browsers are all over the map.
```http
HTTP/1.1 200 YAYAYAYA
foo-TEST: 1
FOO-test: 2
ALSO-here: Mr. PB
ewok: lego
```
Safari ends up with FOO-test, Chrome and Firefox with foo-TEST. Sorting is different. Most other details are the same, including ending in \r\n which goes against the current standard.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/xhr/issues/108#issuecomment-275707105

Received on Friday, 27 January 2017 16:26:38 UTC