Re: [whatwg/xhr] setRequestHeader behavior doesn't seem to match implementations (#108)

Current thinking, assuming the goal is maximum compatibility with deployed rather browsers, rather than a coherent whole:

* Add a space to *combine*'s `,`. Perhaps rename it to *legacy combine* to indicate this is only for old stuff.
* Add a *legacy space flag* to *sort and combine* and *combined value*, that does exactly what you think it might do. (Potentially we do that for *combine* as well, so we can use it for `Access-Control-Request-Headers` and others.)

Updating tests first...

-- 
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-275701285

Received on Friday, 27 January 2017 16:04:23 UTC