Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement: full definitions #1

Open
jrep opened this issue Sep 4, 2015 · 0 comments
Open

Enhancement: full definitions #1

jrep opened this issue Sep 4, 2015 · 0 comments

Comments

@jrep
Copy link

jrep commented Sep 4, 2015

It would be useful to give access to the full definitions of the status codes. Everyone pretty much knows old friends like 200 or 404, but can you really recall the meaning and rules around 204:

The server has fulfilled the request but does not need to return an entity-body, and might want to return updated metainformation. The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant.

If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.

The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.

Perhaps the syntax would be httpstatus -v 205?

Some codes have been added or re-nuanced since the HTTP 1.1 standard first defined them. A more current reference wouldn't be a bad thing.

Update: oh, sorry, "-v [--version]" is taken; how about "-f / --full"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant