I especially like that the entries put front and center the degree to which the official RFCs are actually respected by browsers. That content is all (obviously) in Wikipedia and other sources, but usually buried in a subsection.
Show HN: HTTP Status code directory
11–20 of 23 posts
Re: Show HN: HTTP Status code directory
#12This really needs to clarify the wording on the 300 redirects...
Re: Show HN: HTTP Status code directory
#13This really needs to clarify the wording on the 300 redirects...
Which ones specifically? I had to keep the micro-explanations very short so they only give a very very basic over-view, but the full page explanations should be more than suitable as they're a combination of the Wikipedia explanation and the official IETF explanation (from the RFCs).
Re: Show HN: HTTP Status code directory
#14The source of truth for this is the HTTP Status Code Registry at IANA: http://www.iana.org/assignments/http-status-codes/
It would be really nice if this page could at least refer to it.
Re: Show HN: HTTP Status code directory
#15I think I prefer the lolcat-compliant version: http://httpcats.herokuapp.com/303
Re: Show HN: HTTP Status code directory
#16I think I prefer the lolcat-compliant version: http://httpcats.herokuapp.com/303
I like the idea of adding that, I could also include httpstat.us in the same way, here's an example of how I think I'll do it (under code references): http://httpstatus.es/101
will complete that in the morning.
Re: Show HN: HTTP Status code directory
#17I think I prefer the lolcat-compliant version: http://httpcats.herokuapp.com/303
Or the f7u12 version: http://www.httprage.com/
Re: Show HN: HTTP Status code directory
#18This really needs to clarify the wording on the 300 redirects...
Which ones specifically? I had to keep the micro-explanations very short so they only give a very very basic over-view, but the full page explanations should be more than suitable as they're a combination of the Wikipedia explanation and the official IETF explanation (from the RFCs).
Well, for 304 the explaination is "this and all future requests should redirect to given URI", which is just wrong. Simply "Not modified" would be better.
Re: Show HN: HTTP Status code directory
#19How many wikipedia pages can we turn into .es domains? http://en.wikipedia.org/wiki/List_of_HTTP_status_codes On a side note, I need to start using 418 "I'm a teapot" more often.
Coincidentally I just set up a response that uses 418 I'm a teapot about an hour ago. I really wanted 422 Unprocessable Entity, but werkzeug doesn't implement that (and for some reason instead implements 418 I'm a teapot).
It doesn't implement that? https://github.com/mitsuhiko/werkzeug/blob/master/werkzeug/_...
Re: Show HN: HTTP Status code directory
#20What's wrong with the first Google's response for "HTTP status codes" (i.e. http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html )?
Part of my job is user support and a frequent problem is users not sure what a server error means, when explaining I like to provide sources for explanations I give. I don't like linking to the RFCs or wikipedia because they can be overwhelming/confusing for people who aren't particularly competent with technology. The original aim for this site was to have explanations in layman terms that anyone could understand an…
What user would ever care what a status code means? For users, there are two status codes: "200 OK" and "^200 Not OK and the webmaster has been notified"