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

@mnot You are providing an API that has handled the implementation of HTTP by being case sensitive up until this update.   Most applications echo'd the HTTP specifications for Headers and followed the casing in the spec.  Can you point out 10 major HTTP 1.0/1.1 server's in production use that don't send 'Content-Type' for the Content-Type header?  Note the casing.  By forcing lower case you are forcing everyone to lowercase every header or have a conditional when evaluating every header.  That is as case sensitive as the code example that I posted is.  

If you made the headers array TRULY case insensitive e.g. request.headers['Content-type'] request.headers['content-type'] request.headers['Content-Type'] request.headers['Content-tYpe']  all come back with the same value - well then you have a change that is fit for global deployment.  Why can't/wasn't that implemented since it is a case sensitivity problem?

If this was an HTTP2 introduction then my main problem is with whoever hates capital letters on the HTTP2 spec team.  

@RByers  I appreciate your desire to roll this out worldwide but what the heck man?  Why the rush?

-n







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