Live data from Hacker News

Series of posts on HTTP status codes (2018)

evertpot.com

11–13 of 13 posts

Re: Series of posts on HTTP status codes (2018)

#11
One of the most irritating bugs in client libraries is if they hard-code 1xx behavior to particular numbers, rather than treating the entire range uniformly.

This makes it easy to desync, though since it's not the server end it's rarely as catastrophic.

To fix this, servers need to start returning bogus 199 Fix Your Client headers before a random fraction of all real responses.

Re: Series of posts on HTTP status codes (2018)

#13
post #2

Dang these are much more useful than my first port of call for looking up http codes... which is http.cat/ . 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

Always check MDN - for web stuff they truly are the best reference out there.
Post reply on HN