If your application involves IIS, or HTTP requests, an exception is very normal. Corresponding to the HTTP protocol, the response may return different error code values.
There must be clear
200 is normal, between 400 to 500, have an abnormality, IIS can be handled, such as 403 no permissions, 404 files do not exist, 500, IIS processing unnecessary abnormality. Specific status reference: http:///www.w3.org/ Protocols / RFC2616 / RFC2616-Sec10.html # SEC10
For returning exceptions and the specific details you requested,
On the client, you can use the network monitor or IEHTTPHEADERS. About this tool, you can download from http://www.blunchrs.html.
After downloading, you can see each specific HTTP request.
such as:
We visited the internal forum and you can see the HTTP request information.
For the server, it is mainly to see the log of IIS. This log is placed under System32 / LogFiles. If there are multiple directory if you are multiple application pools or sites, you can judge the corresponding log, or use the network monitor Or you can intercept more network traffic information.
such as:
About these two tools:
IEHTTPHEADER can view usage and download from http://www.blunch.html. Network Monitor, Windows Optional Components, 2000 and 2003 support, how to install and use, reference http://www.winnetmag .com / article / articleid / 37504 / 37504.html
