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

Oh, I see, actually.  We _do_ kinda do case-folding but it's rather bizarre.  When we first see a header name, we intern it; the key is the header string and the interned value represents that string.  Later if we need to intern a header name, we intern _that_ and this check does a case-insensitive match on the key, but returns whatever the value is.

So afaict once we see a "foo-TEST" header we will treat all header names that are just different casings of it as "foo-TEST" or so.

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