Troubleshoot-TestingDebugging
Troubleshoot-TestingDebugging
Page 2 of 10
Page 3 of 10
Page 4 of 10
Page 5 of 10
Microsoft's IIS 7.0, IIS 7.5, and IIS 8.0 servers define the following HTTP substatus codes to indicate a more specific cause of a 404 error:
Page 6 of 10
404.12 – Request contains high-bit characters.
404.13 – Content length too large.
404.14 – Request URL too long.
404.15 – Query string too long.
404.16 – DAV request sent to the static file handler.
404.17 – Dynamic content mapped to the static file handler via a wildcard MIME mapping.
404.18 – Query string sequence denied.
404.19 – Denied by filtering rule.
404.20 – Too Many URL Segments.
Page 7 of 10
Page 8 of 10
500 Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.[63]
The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-
service API).[64]
Page 9 of 10
The server was acting as a gateway or proxy and received an invalid response from the upstream server.[65]
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[66]
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.[67]
The server does not support the HTTP protocol version used in the request.[68]
The server is unable to store the representation needed to complete the request.[17]
The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
Further extensions to the request are required for the server to fulfil it.[70]
The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to
require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).[59]
Page 10 of 10