httpstatusview v1.0.2

CREATED BY: AJ_Chambers-@-KATANA_DEVELOPMENT

HTTP Status Codes Defined:

400: The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).

401: Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.

403: The request contained valid data and was understood by the server, but the server is refusing action. This may be due to the user not having the necessary permissions for a resource or needing an account of some sort, or attempting a prohibited action.

404: The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

405: A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.

408: The server timed out waiting for the request.

500: A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501: The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (ex.

a new feature of a web-service API).

!end of 'README.me'!