Troubleshooting HTTP 401.3 errors with Process Monitor

Last week I posted the following blog which showed how to use Process Monitor to troubleshoot service startup issues. http://blogs.msdn.com/webtopics/archive/2009/06/16/troubleshooting-service-startup-issues-with-process-monitor.aspx To continue on that topic, I ran across another issue recently where Process Monitor was again very helpful in troubleshooting. Problem – When browsing ASP pages, we were getting below error in the browser. Browsing…

1

Troubleshooting HTTP Compression in IIS 6.0

Cross-posted from http://blogs.msdn.com/mike    Enabling HTTP Compression for your IIS6 web applications is one way of increasing site performance.  One of the more common problems I see when helping customers with compression is that their IIS servers are not set up for compression correctly.  Unfortunately the IIS6 admin GUI doesn’t expose many of the compression…

3

HTTP 400 Bad Request when client terminates request headers improperly

  After sending an HTTP request to IIS, an Internet Explorer client displayed the following error message to the user:   Bad Request     Beginning in IIS 6.0, “Bad Request” errors are almost always returned by HTTP.sys, so the next step was to look in the httperr.log file for further evidence of the failure…

1

How to troubleshoot HTTP 400 errors

  After sending an HTTP request to an IIS server, an HTTP client (such as Internet Explorer) may display the following type of error message in the browser window:       If Internet Explorer’s Friendly HTTP Error Messages option is turned off, the error may resemble the following:         In these…

5

Removing an IIS server's IP address from HTTP responses

  Introduction The purpose of this blog post is to discuss how to mask an IIS server’s IP address from being sent as part of an HTTP response.  By default, IIS can send a server’s IP address in the Content-Location or Location response headers of a response.  Beginning in Windows 2003 SP1, you can configure…

3