Series of posts on HTTP status codes (2018)
evertpot.com
Series of posts on HTTP status codes (2018)
1–10 of 13 posts
Re: Series of posts on HTTP status codes (2018)
#2Dang 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 /404Re: Series of posts on HTTP status codes (2018)
#3Title 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)
Re: Series of posts on HTTP status codes (2018)
#4Dang 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
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
Re: Series of posts on HTTP status codes (2018)
#5Dang 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
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
Was going to post this, the Mozilla content is great.
Re: Series of posts on HTTP status codes (2018)
#6Title 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)
Also, it is slightly outdated as it does not incorporate RFC9110 which renames some status codes which previously were WebDAV-only:
Re: Series of posts on HTTP status codes (2018)
#7Title 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)
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.
Re: Series of posts on HTTP status codes (2018)
#8I read the url as: ever t-pot, as a reference to 418.
Turns out it's the author's actual name.
Re: Series of posts on HTTP status codes (2018)
#9It's a great idea to blog through a "mundane" thing like this. You learn alot and have an impetus and won't run out of ideas to blog. There is always another status code! You could do the same with other things. E.g. programming languages or whatever.
Re: Series of posts on HTTP status codes (2018)
#10Dang 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