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 service startup issues with Process Monitor

Many things can cause a service, like IIS’s World Wide Web Publishing Service, to fail on startup. When troubleshooting such an issue, Process Monitor can be an invaluable tool. What Process Monitor does is monitor all File and Registry access on the system in real-time. The latest version of process monitor can be obtained here….

1

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

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

How to configure URLScan 3.0 to mitigate SQL Injection Attacks

The purpose of this blog post is to review the concept of SQL Injection attacks, to introduce URLScan 3.0, and to discuss how to configure URLScan 3.0 to block a SQL Injection attack that uses the Cookie header of an HTTP request as its attack vector. What is a SQL Injection Attack?There is a wealth…

0