Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
FIX: IP address is revealed in the content-location field in the TCP header in IIS 6.0
Article ID: 834141 - View products that this article applies to.
Important This article contains information about how to edit the metabase. Before you edit the metabase, verify that you have a backup copy that you can restore if a problem occurs. For information about how to do this, see the "Configuration Backup/Restore" Help topic in Microsoft Management Console (MMC).
When Microsoft Internet Information Services (IIS) receives a GET request without a host header, the Web server may reveal the IP address of the server in the content-location field or the location field in the TCP header in the response. This problem may occur if the request does not contain a specific page or if IIS must redirect the original request to another page.
This problem occurs because when IIS receives a GET request that has no host header, IIS must provide a host name or an IP address in the response.
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100Important After you install the service pack, you must set either the UseHostName property or the SetHostName property on the site if you want an alternate host name to be sent for requests. For information about how to do this, see the "" section.
(http://support.microsoft.com/kb/889100/ )How to obtain the latest service pack for Windows Server 2003
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
PrerequisitesNo prerequisites are required.
Restart requirementYou must restart your computer after you apply this hotfix.
Metabase informationAfter you apply this hotfix, you must set either the UseHostName property or the SetHostName property on the site if you want an alternate host name to be sent for requests. For information about how to do this, see the "" section.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Date Time Version Size File name ------------------------------------------------------ 10-Dec-2003 18:07 6.0.3790.91 1,124,352 Iiscfg.dll 10-Dec-2003 18:07 6.0.3790.91 299,008 W3core.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 1.
Warning If you edit the metabase incorrectly, you can cause serious problems that may require that you reinstall any product that uses the metabase. Microsoft cannot guarantee that problems that result if you incorrectly edit the metabase can be solved. Edit the metabase at your own risk.
Note Always back up the metabase before you edit it.
After you install the service pack or apply this hotfix, you must set either the UseHostName property or the SetHostName property on the site if you want an alternate host name to be sent for requests. By default, the same value as the HTTP_HOST variable is sent in the SERVER_NAME variable.
Note If you enable one the following settings, IIS will always use an alternate name for the SERVER_NAME variable.
The data type for the UseHostName property is Boolean. The UseHostName property will instruct IIS to always replace the SERVER_NAME variable with the fully qualified machine name.
Optionally, you can set the SetHostName property. The data type for the SetHostName property is string. Use the SetHostName property if you must specify a host name that is different from the computer name. The SetHostName property assumes that you want this alternate host name. The SetHostName property will cause IIS to ignore the UseHostName setting. You do not have to set the UseHostName property if the SetHostName property is present.
A Web server administrator may use the Adsutil.vbs tool to modify the UseHostName metabase property and the SetHostName metabase property.
Option 1: Set the UseHostName propertyTo set the UseHostName property, follow these steps:
Option 2: Set the SetHostName propertyTo set the SetHostName property, follow these steps:
Mitigating FactorsAfter you set the UseHostName or SetHostName properties in IIS 6.0, it is still possible to see the server’s IP address in an HTTP response. By default, this does not occur. It results from how the response is generated and sent. For example, if you configure an HTTP redirect that results in an HTTP 302 response being sent, and your redirect code uses the server’s IP address, the IP address may appear in the Content-Location or Location header of the response. To work around this issue, do not use the server’s IP address in the redirect logic. Instead, use its host name or fully qualified machine name.
A similar type of behavior can occur if you configure custom error pages to perform a REDIRECT operation and you use IIS Manager to set the redirect target as a URL instead of a file. In this scenario, specify the file instead of the URL to keep the IP address hidden.
The server's IP address can also be sent in an HTTP response if the following conditions are true:
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates