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

One other note.  At least in the case of Gecko, this is all handled in the underlying networking library, not XHR itself.  Which means the "separate with comma and space" is general behavior for headers, and applies to fetch at the moment, and to any network requests that Gecko makes, including ones we don't have ported to be on top of fetch yet.

I would not be surprised if the situation in other engines is similar.

So it might make the most sense to change this in fetch after all...

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