You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"?
The text was updated successfully, but these errors were encountered:
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:
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"?
The text was updated successfully, but these errors were encountered: