Java Reference
In-Depth Information
• 304: Not Modified
• 305: Use Proxy (since HTTP/1.1)
Many HTTP clients (such as Mozilla and Internet Explorer) don't correctly handle re-
sponses with this status code.
• 306 is no longer used, but reserved. Was used for 'Switch Proxy'.
• 307: Temporary Redirect (since HTTP/1.1)
In this occasion, the request should be repeated with another URL, but future requests
can still be directed to the original URL. In contrast to 303, the original POST request must
be repeated with another POST request.
4xx Client Error
The request contains bad syntax or cannot be fulfilled.
• 400: Bad Request
• 401: Unauthorized
Similar to 403/Forbidden, but specifically for use when authentication is possible but has
failed or not yet been provided. See basic authentication scheme and digest access authenti-
cation.
• 402: Payment Required
The original intention was that this code might be used as part of some form of digital
cash/micropayment scheme, but that has never eventuated, and thus this code has never
been used.
• 403: Forbidden
• 404: Not Found
• 405: Method Not Allowed
• 406: Not Acceptable
• 407: Proxy Authentication Required
• 408: Request Timeout
• 409: Conflict
• 410: Gone
• 411: Length Required
• 412: Precondition Failed
• 413: Request Entity Too Large
• 414: Request-URL Too Long
• 415: Unsupported Media Type
• 416: Requested Range Not Satisfiable
• 417: Expectation Failed
• 449: Retry With
A Microsoft extension: The request should be retried after doing the appropriate action.
5xx Server Error
The server failed to fulfill an apparently valid request.
• 500: Internal Server Error
• 501: Not Implemented
• 502: Bad Gateway
