Custom Search

Wednesday, 30 October 2013

SOME HTTP status codes

SomeTimes we Meet Such Type of Error Code Like

404 Not Found
500 Internal Server Error
403 Forbidden


100 Continue
101 Switching Protocols


200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content


300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
307 Temporary Redirect


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 Time-out
409 Conflict
410 Gone
411 Length Required
412 Precondition Failed
413 Request Entity Too Large
414 Request-URI Too Large
415 Unsupported Media Type
416 Requested range not satisfiable
417 Expectation Failed


500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Time-out
505 HTTP Version not supported


CODE 5XX Details

5xx - Server error

These HTTP status codes indicate that the server cannot complete the request because the server encounters an error.

> 500 - Internal server error.

Following HTTP status codes that indicate a more specific cause of a 500 error:



500.0 - Module or ISAPI error occurred.
500.11 - Application is shutting down on the web server.
500.12 - Application is busy restarting on the web server.
500.13 - Web server is too busy.
500.15 - Direct requests for Global.asax are not allowed.
500.19 - Configuration data is invalid.
500.21 - Module not recognized.
500.22 - An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
500.23 - An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
500.24 - An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
500.50 - A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
Note Here is where the distributed rules configuration is read for both inbound and outbound rules.
500.51 - A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
Note Here is where the global rules configuration is read.
500.52 - A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
500.53 - A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.
500.100 - Internal ASP error.

 501 - Header values specify a configuration that is not implemented.
 502 - Web server received an invalid response while acting as a gateway or proxy. 

Following HTTP status codes that indicate a more specific cause of a 502 error:

502.1 - CGI application timeout.
502.2 - Bad gateway: Premature Exit.
502.3 - Bad Gateway: Forwarder Connection Error (ARR).
502.4 - Bad Gateway: No Server (ARR).

> 503 - Service unavailable.

Following HTTP status codes that indicate a more specific cause of a 503 error:

503.0 - Application pool unavailable.
503.2 - Concurrent request limit exceeded.
503.3 - ASP.NET queue full

No comments:

Post a Comment

LinkWithin

Related Posts Plugin for WordPress, Blogger...