Re: [whatwg/xhr] Web compat implications of making getAllResponseHeaders lowercase (#146)

this is not an http/2 issue. The header name is case insensitive in both versions of http. The original query I responded to asked how to handle the transition, and that answer is easy because the semantics of http are the same independent of http version or xhr implementation - the header name is not case sensitive, so just use a case insensitive comparison to get reliable operation. If your app isn't doing that it should be fixed like any other discovered latent bug (we've all got them.).

I don't have a strong opinion on whether there are sufficient legacy problems here to warrant a particular xhr implementation.


-- 
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/146#issuecomment-319428530