Contents |
client in front of the proxy. Source: unknown? ← Return to httpstatuses.com
codes HTTP status codes Below is a list of response codes for HTTP returned by servers on the Internet. Most of these status codes are specified by RFC 2616, while some are unstandardized status codes which nginx 599 are also used on the web. The codes help identify the cause of the
problem when a web page or other resource does not load properly. The response code ranging from 1XX to 5XX. 1xx Informational http 598 Responses HTTP status codes in the 1xx are typically informational. 100 Continue 101 Switching Protocols 102 Processing 103 Checkpoint 122 Request-URI too long 2xx Successful Responses Status codes in the 2xx range indicate that the transaction was https://httpstatuses.com/599 received, understood, accepted and processed successfully. 200 OK 201 Created 202 Accepted 203 Non-Authoritative Information (since HTTP/1.1) 204 No Content 205 Reset Content 206 Partial Content 207 Multi-Status (WebDAV) (RFC 4918) 226 IM Used (RFC 3229) 3xx Redirection Responses HTTP status codes in the 3xx range pertain to redirection. The client must take additional action to complete the request. 300 Multiple Choices 301 Moved Permanently 302 Found 303 See Other (since HTTP/1.1) 304 Not http://www.ascii-code.com/http-status-codes.php Modified 305 Use Proxy (since HTTP/1.1) 306 Switch Proxy 307 Temporary Redirect (since HTTP/1.1) 308 Resume Incomplete 4xx Client Error HTTP status codes in the 4xx range indicate that a problem occurred with the request. 400 Bad Request 401 Unauthorized 402 Payment Required 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-URI Too Long 415 Unsupported Media Type 416 Requested Range Not Satisfiable 417 Expectation Failed 418 I'm a teapot (RFC 2324) 422 Unprocessable Entity (WebDAV) (RFC 4918) 423 Locked (WebDAV) (RFC 4918) 424 Failed Dependency (WebDAV) (RFC 4918) 425 Unordered Collection (RFC 3648) 426 Upgrade Required (RFC 2817) 428 Precondition Required 429 Too Many Requests 431 Request Header Fields Too Large 444 No Response 449 Retry With 450 Blocked by Windows Parental Controls 499 Client Closed Request 5xx Server Error Error codes in the 5xx range indicate that server is aware that it has encountered an error or is otherwise incapable of performing the request. 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 505 HTTP Version Not Supported 506 Variant Also Negotiates (RFC 2295) 507 Insufficient Storage (WebDAV) (RFC 4918) 509 Bandwidth
enter a title. You can not post a blank message. Please type your message and try again. 5 Replies Latest reply: Jun 11, 2014 12:39 PM by tinghche Handle https://communities.cisco.com/thread/42941?start=0&tstart=0 AXL 599 error message istibekesi Apr 15, 2014 6:27 AM Tweet Hi All,I was wondering, if i send a wrong request to CUCM AXL, for example a 10.0 version request to CUCM 9.0... the response is:httpStatus code 599 which is fine.And the error content (basically the error stream) is a "nice" error message in HTML error 599 format.The error is clear and nice to read in browser:
type: Status report
message: The specified version is not available. Available versions are 7.1, 8.0, 8.5, 9.0 and 9.1
description: http.599
But how i can get only the descriptive error message somehow? I mean only the cont