I sold httpstatuses.com (website and domain) in... 2016 I think, maybe 2017, and the acquirers kept it as-is until 2022. Someone (not me) recently relaunched the site (as it was opensource) under a new domain -- https://httpstatuses.io -- so if you can replace ".com" with ".io" in your muscle memory, you can get the original site!
You can actually just do without the keywords: it's easy to figure out what is intended since class will never reach 100, and code will never go under 100. Will make this more intuitive to use since there's nothing to remember.
I've had great success using this sort of know-your-data "smart" search on company-internal databases for customers. People like it because it's intuitive and they don't need to remember keywords or mess with dropdowns.
Completely agree. The pollution metaphor is apt: Not only the cognitive cost of looking over this code, realizing it’s displaying a CSV, and offering advice but also the real CO2 cost of hosting, packaging, distributing, running, and maintaining this code. Truly progressive devs should always consider these costs.
You want to bring up pollution, what about the plethora of http status reference sites we already have. At least OP kept it to CLI. It’d be nice if it sourced it from Mozilla so it wouldn’t need updating.
The recommendation does not hold up when scrutinised.
MDN is also third-party, thus equally unofficial. The official sources are IANA and IETF.
The quality is objectively worse compared with webconcepts. It's not immediately visible where a status code originates from, and when you follow through to the detail document, you can see that the outdated RFC 2616 is referenced.
The "rando" is a long term contributor to Web specifications.
The choice of top-level domain has zero significance, as I said previously, the only measure of official(?:ness|ity) is where the information originates from.
This comment is completely unnecessary and adds nothing to the discussion. How is the author publishing source code on his own github repo "burdening the public".
I took a slightly different approach to this problem.
I made a CLI tool (bash) that leverages imgcat (the one that comes with iTerm2) to display images (in my terminal) from http.cat that correspond to the code I'm wondering about as well as a link to the mozilla docs with more details if i need them.
seeing the cats injects a smile into the frustration around "what the heck is a 407?!"
40 comments
[ 3.5 ms ] story [ 95.2 ms ] threadFor those that think that `man` is only about commands, we already have `man 7 ascii`.
Their blog post about reviving the project: https://jkulton.com/2022/reviving-httpstatuses
I use a bash function to load the MDN page for the status:
I've had great success using this sort of know-your-data "smart" search on company-internal databases for customers. People like it because it's intuitive and they don't need to remember keywords or mess with dropdowns.
Also, why don't you just call it http?
https://httpie.io/docs/cli/usage
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
You want to bring up pollution, what about the plethora of http status reference sites we already have. At least OP kept it to CLI. It’d be nice if it sourced it from Mozilla so it wouldn’t need updating.
MDN is also third-party, thus equally unofficial. The official sources are IANA and IETF.
The quality is objectively worse compared with webconcepts. It's not immediately visible where a status code originates from, and when you follow through to the detail document, you can see that the outdated RFC 2616 is referenced.
The choice of top-level domain has zero significance, as I said previously, the only measure of official(?:ness|ity) is where the information originates from.
Currently, you're polluting the discussion for this submission by continuing to post in the subthread of an already-flagged comment.
Please stop.
.bashrc:
httpcode () { python3 -c "from http import HTTPStatus; print(HTTPStatus($1))" }
HTTPStatus($1).name.title().replace('_',' ')
⌘ https://codeberg.org/kas/httperr
I made a CLI tool (bash) that leverages imgcat (the one that comes with iTerm2) to display images (in my terminal) from http.cat that correspond to the code I'm wondering about as well as a link to the mozilla docs with more details if i need them.
seeing the cats injects a smile into the frustration around "what the heck is a 407?!"
https://github.com/masukomi/masuconfigs/blob/master/bin/http...
It's definitely not complete, but very helpful to decide which status code makes sense for a particular situation.
Now I just go to http.cat.
Why not simply do this?
$ hssp 204
$ hssp 2 -- lists everything under it
https://www.httpstatuses.org/
P.S. For some reason I can't remember if 301 or 302 is the permanent one.
P.P.S. I hate the fact that 401 should be Unauthenticated (instead of Unauthorized), and 403 should be Unauthorized (instead of Forbidden).