rmaake1 / httpstatuses Goto Github PK

SEO tools complain about the lack of meta tags, which is probably a fair complaint.

I think it's very annoying to either have to hover over the code or click it to discover what it actually stands for (what it's official name is).

Couldn't this just be displayed next to the code like this?

307: TEMPORARY REDIRECT

Some improvements could be made to the site design

• Differentiate between standard and non-standard status codes on the homepage
• Address link targets being too small on mobile (according to Google)
• Improve Code References display

• http://stackoverflow.com/questions/8966740/how-to-host-google-web-fonts-on-my-own-server
• https://news.ycombinator.com/item?id=8802395
• http://brick.im/fonts/
• http://www.localfont.com/

http://en.wikipedia.org/wiki/List_of_HTTP_status_codes#451

Although not official like the activesync one, unavailable for legal reasons might also be interesting.

See also http://qz.com/111211/how-a-simple-three-digit-number-helps-websites-stick-it-to-online-censorship/

There's a couple of different use cases for httpstatus.es, to my mind they are:

• A developer looking for the right status code for their situation, eg: "What status code do I use when my resource has moved permanently?"
• A person interested in learning about the various status codes, not necessarily for development reasons
• A person looking for the meaning of a status code, knowing only the code or name

The likelihood that someone is visiting a status code page for an overview of the status code seems greater than the likelihood that someone is looking for specific implementation details.

When a person visits a status code that has a large description from the RFC detailing implementation it could be quite intimidating, and may mislead the visitor into believing they need to read and understand everything to know what the status code means. For example 204 No Content has 1 paragraph that describes why someone might encounter or need the status code -- in easy to understand terms for a non-developer --, and then 6 paragraphs detailing implementation.

Should the full descriptions (implementation details) be hidden behind some sort of "Read more..." or "Show implementation details" (with inline content reveal) instead of presenting all of the information to every visitor?

• If someone reveals implementation details once should they default to display every time?
• Each status code description will need to be reviewed to ensure that the opening paragraph doesn't include implementation details

Hi!

Can i translate this docs to Brazilian Portuguese, and host in a subdomain here on github?

The soft line length limit doesn't really make sense if people are encouraged to contribute via the GitHub editor, and anyone using their own IDE / text editor can configure that to wrap lines.

• Remove requirement from the contribution guidelines
• Edit each Markdown file to conform

Earlier, you could access individual status code information (in JSON) by accessing http://httpstatus.es/codes/{category}.json where {category} was whatever the status code started with (4 for 404, etc.)

Has the API endpoint changed or completely removed?

The wikipedia page for HTTP Status Codes references httpstatus.es, but that doesn't make much sense since the value of the website is that it takes information from various sources and presents it well, Wikipedia should be referencing the sources.

There are more code that could be added...

• 103
• 306
• 420
• 425
• 430

the site responds with 403 for certain queries, eg. https://httpstatuses.com/?foo=http://.

we have a content management system where every outbound link is tagged with utm params (for seo reasons), and we noticed that links to httpstatuses.com respond with 403. i think you should just discard every query param, as they are not used anywhere on the site.

At present the domain httpstatus.es is the primary domain of the site, and httpstatuses.com is a 301 redirect to httpstatus.es. The httpstatus.es domain is cute, but according to this Google don't consider .es to be generic, meaning there are some search engine disadvantages to running an international site on .es. Search engines are the majority source of traffic for the website.

Switching the domains around (httpstatus.es/200 -> httpstatuses.com/200) shouldn't have any negative consequences, and would just be a matter of adjusting the web server configuration and buying a new SSL certificate.

• Purchase SSL certificate for httpstatuses.com
• Set up httpstatus.es as a 301 redirect to httpstatuses.com
• Change httpstatus.es to httpstatuses.com in templates etc.
• Rename GitHub project to httpstatuses.com (or just httpstatuses -- the repository can be a useful place to reference status codes too, it's not essential to visit the website?)

To verify site works correctly upon switch, the following must be true:

• https://httpstatuses.com/200 displays the 200 status code page
• httpstatuses.com/200 redirects to https://httpstatuses.com/200
• www.httpstatuses.com/200 redirects to https://httpstatuses.com/200
• https://www.httpstatuses.com/200 redirects to https://httpstatuses.com/200
• httpstatus.es/200 redirects to https://httpstatuses.com/200
• www.httpstatus.es/200 redirects to https://httpstatuses.com/200
• https://httpstatus.es/200 redirects to https://httpstatuses.com/200
• https://www.httpstatus.es/200 redirects to https://httpstatuses.com/200

There are more code that could be added...

• 103
• 306
• 420
• 425
• 430

As status code 418 => "I'm A Teapot" was removed from Rack at https://github.com/rack/rack/blob/master/lib/rack/utils.rb#L552, the Rails status symbol :i'm_a_teapot does not exist anymore. The new status to symbol code message.downcase.gsub(/\s|-|'/, '_').to_sym would have made it :i_m_a_teapot, by the way.

Version 2 (on the metalsmith branch) is almost ready.

Before:

• Visit each page from the old site (as per google analytics) on the new site and verify the results are as expected
• Set up httpstatuses.com to redirect to httpstatus.es
• Switch deploy.sh to listen on the master branch
• Switch DNS for httpstatus.es from old server to new server

After:

• Let Runscope know about the new version so they can update the screenshot on their community projects page
• Close open pull requests against Version 1 and apologise to those who contributed for my (temporary) abandonment of the project

As per this issue from 2014 the descriptions are out of date, update the descriptions to the latest standards. Also, once the new descriptions have been added, adapt them to fit the "simple description" httpstatus.es aim by splitting the most pertinent information into an introductory paragraph (which will be emphasised on the page).

• 100
• 101
• 102
• 200
• 201
• 202
• 203
• 204
• 205
• 206
• 207
• 208
• 226
• 300
• 301
• 302
• 303
• 304
• 305
• 307
• 308
• 400
• 401
• 402
• 403
• 404
• 405
• 406
• 407
• 408
• 409
• 410
• 411
• 412
• 413
• 414
• 415
• 416
• 417
• 418
• 421
• 422
• 423
• 424
• 426
• 428
• 429
• 431
• 499
• 500
• 501
• 502
• 503
• 504
• 505
• 506
• 507
• 508
• 510
• 511
• 599

Wondering why this brilliant website now redirects to an inferior website. Did the domain expire? or is the redirect intended?

I found this amusing; and had to do some googling before I could figure out what it is.

Really useful project, it would be great if the site was responsive so it was easier to view on mobile devices.

If you add the un-minified CSS I wouldn't mind having a go at it.

The current message is part of the content which I don't like much, I think the message could be better placed, both to increase awareness (what is Runscope? why is it sponsoring this site?) and not be mixed in with the content. A banner at the top of the page in blue with white text might look and convert better, and could be included on every page -- not sure about this, need to think about it.

The status code 599 is non-standard, it doesn't exist in any RFC, but it appears to be quite widely used, it's the 10th most popular status code on the website. The description I originally used came from wikipedia, now the wikipedia page has been updated with circular references, and my google searches aren't returning much useful information on where the code came from, or who's using it... but it must be someone!

Any research / input here is greatly appreciated.

rails can use these symbols to better name a status code
reads better

http://guides.rubyonrails.org/layouts_and_rendering.html#the-status-option

wanted to show it, maybe as additional info
or would that be out of scope ?

In June the HTTP 1.1 spec RFC 2616 got replaced by a bunch of new updated revision, RFC 7230 to 7235: https://www.mnot.net/blog/2014/06/07/rfc2616_is_dead

The one related to status codes is RFC 7231 which also references a new status code registry at http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

Currently status codes like 503, http://httpstatus.es/503, references the old RFC 2616 and even though there in most cases are no differences (the Appendix B of RFC 7231 outlines which status code that has seen changes) it would be good to have the references updated so that one can know for sure that the description is an up to date one.

Quite a few people tweet about the site, however when the site had a click to tweet button the number of tweets was much greater. A tweet button provides value to the site (increased exposure) and value to users (some tweet to save things).

These should not use any sort of Javascript widget, they should be simple links, no need to add additional dependencies.

• Twitter click to tweet
• Slack "share to channel" -- does this exist? is there a url I can use?
• Pinboard bookmark
• GitHub star button (instead of link to repository? just link to repository?)

Would be nice to add a favicon, what you think? :)

I'm getting a 404 when I try to view details about any of the http statuses on https://httpstatus.es/!

Example URL: https://httpstatuses.com/408

Apparently Apache is having trouble finding a 404 error page to display too.

https://www.iana.org/assignments/http-warn-codes/http-warn-codes.xhtml

via @lukegb

edit: nevermind, I think luke was playing a trick on me. Nobody uses these.

Returning something like that

{
  "code": 404,
  "message": "Not Found"
}

or even better, whole page to be represented as json, for example including the text description, and code references.

{
  "code": 404,
  "message": "Not Found",
  "description": "A 404 status code does not indicate whether this lack of...",
  "references": [
    "Rails HTTP Status Symbol :not_found",
    "Go HTTP Status Constant http.StatusNotFound"
  ]
}

The current favicon is ugly and uninspired. I'd like to either create or commission a new logo that can be used for the Favicon and be available for use as a logo should a logo be needed in future.

Seems like you could cut your hosting costs and ditch the sponsorship by making this into a Jekyll site hosted in GitHub Pages.