Hacker News Reader

Comment by est31 | Hacker News Reader

I'm still not over the fact that they made headers all-lowercase in HTTP/2. I know the reasons, but it's so weird to have all-lowercase headers. TBH I don't see much of an uptake in the community either: since HTTP/2 came out, I've barely seen lowercase headers be proliferated in documentation of headers, e.g. MDN lists them HTTP/1 style: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers

View on HN

Anything working with headers should always have been case insensitive, so there's no reason to update the any documentation.

As someone who works in infrastructure I disagree with this. While it’s true that applications should always have done this, many many do not and need to be dealt with. If they are third party paying customers, your only option is to figure out how to make things work, because asking customers to upgrade will piss many of them off.

The simple fact so many applications do not treat headers as case insensitive is one of the major things holding back http 2. With HTTP/1 it was suggested but not enforced. Upgrading to http/2 with forced-lowecasing breaks these applications

What part are you disagreeing with?

Someone should write a DevTools extension that uppercases the headers, if such a thing is possible. :)

If you want to break protocol, I suggest that we also change all of the HTTP verbs for no reason whatsoever :^)

GET -> FETCH

HEAD -> EXAMINE

POST -> SUBMIT

PUT -> REPLACE

DELETE -> REMOVE

CONNECT -> PROXY

OPTIONS -> ALTERNATIVES

TRACE -> ECHO

PATCH -> PARTIALUPDATE

Stop trying to make FETCH happen.

Need to consult specialists from Stanford, because word "Submit" is inappropriate!

ref: https://news.ycombinator.com/item?id=34039816

They should ofc have used

SELECT CREATE UPDATE DELETE SUBMIT

and nothing more :D

#TheWebThatNeverWas https://youtu.be/8JOD1AQGqEg?t=1240

HEAD, POST and PUT replacement are actually nice and better than the originals :) (at least for a non-native speaker of English).

Why ALTERNATIVES for OPTIONS?

I just meant for display... :( Like it changes content-type to Content-Type, which shouldn't break anything right...?? HTTP headers are supposed to be case insensitive anyway right?

If the Chromium/Chrome browser is open source then anyone should able to edit the source code to change the headers to whatever case they prefer and re-compile.

Reply on news.ycombinator.com