NHacker Next
login
▲Series of posts on HTTP status codes (2018)evertpot.com
48 points by antonalekseev 2 days ago | 7 comments
Loading comments...
AriedK 2 hours ago [-]
I read the url as: ever t-pot, as a reference to 418. Turns out it's the author's actual name.
VoidWhisperer 7 hours ago [-]
Title should probably be updated to include the fact that this is from 2018 (relevant as this series has been completed as opposed to having just been started)
roywashere 6 hours ago [-]
Also, it is slightly outdated as it does not incorporate RFC9110 which renames some status codes which previously were WebDAV-only:

https://github.com/python/cpython/pull/117611

smartmic 4 hours ago [-]
Correct (and already done by now). Just a few days ago, there was the remarkable example that Cloudflare wants to use the code 402 (payment required) to keep AI crawlers away or ask them to pay. I still think it's a great idea, hopefully something will come of it.

https://news.ycombinator.com/item?id=44432385

Untit1ed 7 hours ago [-]
Dang these are much more useful than my first port of call for looking up http codes... which is http.cat/<code>. It's a shame you have to know what a code is to get to it... e.g. /404-not-found works instead of /404
dylan604 7 hours ago [-]
the MDN article on response codes is my default

https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...

You don't need to know the name. You can increment the URL directly as well

jdwithit 6 hours ago [-]
Was going to post this, the Mozilla content is great.