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

Hi,

Thanks for taking our [issue](https://bugs.chromium.org/p/chromium/issues/detail?id=749086#c7) in consideration.
As mentioned by @RByers, this is a major application breakage for us. We are an on-premises and open source Low-code development platform. Meaning that users install our platform on site and build web applications with.
This change makes not only our platform unusable but also the application created by our users.

Let's take a small example: we build our pagination components around the 'Content-Range' response header. Obviously header['Content-Range'] is now undefined so our pagination is not displayed anymore.

This is the same for all response headers we use including a CSRF token mandatory for all our APIs calls.

When reading the [specification](https://xhr.spec.whatwg.org/#the-getallresponseheaders%28%29-method) I can't see any place saying that getAllResponseHeaders()  must returns header names in lower case, furthermore since HTTP2 servers must return header in lower case getAllResponseHeaders() will return header in lower case for this specific protocol.

We know that we need to change some code to support HTTP2 and this is totally acceptable for us, nevertheless we would expect xhr API to stay stable for HTTP1 protocol so legacy applications don't break.

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