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

> I agree it's nice to do lowercasing, but as @cpuy notes, as a developer, you would expect the XHR-function to be stable, to prevent applications from breaking down all of a sudden...

There is no guarantee that browsers will keep header casing consistent over time.
WebKit (and probably other browsers as well) are not always propagating network response header casing to XHR, and this propagation is probably not consistent between browsers.
Header casing may break at any browser/network stack/intermediary level.

Lowercasing makes sense to me.
I am not sure how we can best handle the transition though.

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