Custom HTTP headers are inherited from a website after running aspnet_regiis.exe on Internet Information Services (IIS) 6.0

Article translations Article translations
Close Close
Article ID: 2321027 - View products that this article applies to.
Expand all | Collapse all

SUMMARY

Consider the following scenario. You have custom HTTP headers configured for your IIS 6.0 Web site. By default, these custom headers get inherited to the applications or virtual directories underneath this web site. However, you have specifically removed these headers from the application or virtual directory levels. You run aspnet_regiis.exe with the install (-i), uninstall (-u) or repair (-iru) switches. During the aspnet_regiis.exe routine, your custom HTTP headers will be added back to the applications or virtual directories in question. These newly added headers are essentially the headers that are present at the parent web site level.


MORE INFORMATION

This behavior only occurs on Windows Server 2003 running IIS 6.0. Simply remove the unwanted headers from the application or virtual directory configuration if they re-appear after running aspnet_regiis.exe. 


Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 2321027 - Last Review: August 11, 2010 - Revision: 4.0
APPLIES TO
  • Microsoft Internet Information Services 6.0
Keywords: 
KB2321027

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com