Microsoft

# Remove Unwanted HTTP Response Headers

The purpose of this blog post is to discuss how to remove unwanted HTTP response headers from the response. Typically we have 3 response headers which many people want to remove for security reason.

• Server - Specifies web server version.
• X-AspNet-Version - Specifies the version of ASP.NET used.

Before you go any further, you should evaluate whether or not you need to remove these headers. If you would like to go ahead and remove the headers then follow the following options.

There are three ways to remove the Server header from the response. The best one is to use the third option.

1. Using the Registry key.

Create a DWORD entry called DisableServerHeader in the following Registry key and set the value to 1.

HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

After adding the Registry key, restart the HTTP service using the net stop http command and the net start http command. If the HTTP service doesn’t start up then use the iisreset command. If that also doesn’t work then you can restart the server.

Please note that this method is used only when the Server header comes as “Microsoft-HTTPAPI/2.0”.

When the request comes to IIS, it is first goes to http.sys driver. HTTP.SYS driver either handle the request on its own or send it to User mode for further processing. When the request goes to User mode that’s the time it returns the server header as “Microsoft-IIS/7.5.”.

However when the request returns from the HTTP.SYS driver then the server header comes as “Microsoft-HTTPAPI/2.0”. By placing the above registry key it will remove this specific header

If you would like to remove the Server header as “Microsoft-IIS/7.5.”, then follow the following methods.

2. Using the URLScan tool.

After installing URLScan, open the URLScan.ini file typically located in the %WINDIR%\System32\Inetsrv\URLscan folder. After opening it, search for the key RemoveServerHeader . By default it is set to 0, but to remove the Server header, change the value to 1.Doing so will remove the Server header Server: Microsoft-IIS/7.5 from the User mode response.

Please note that changes made by URLScan at global level apply to all of your sites. If you would like to setup this for particular site then look at the following article (site filter section)

http://www.iis.net/learn/extensions/working-with-urlscan/urlscan-setup

3. Using URLRewrite

If you don’t want to go with URLScan, you can use the URLRewrite module to remove the value of the Server header. Please note that it will not remove the header all together but it will remove the value of it.

Step 1. Install URLRewrite. To install the URLRewrite please go to the following link

Step 2. Open the site on which you would like to remove the Server header and click on the URLRewrite section.

Step 3. Click on the “View Server Variables” in the Actions pane in the right hand side.

Step 4. Click on the Add button and then enter “RESPONSE_SERVER” in the textbox provided.

Step 5. Now we need to create an outbound rule. To know how to create an outbound rule, look at the following link

http://www.iis.net/learn/extensions/url-rewrite-module/creating-outbound-rules-for-url-rewrite-modul...

Step 6. Create an Outbound rule as the following.

Please note that this is a website-specific rule. If you want to create the rule for all of your applications, create the rule at the server level. Also, some applications, especially third party applications, may require the Server header, so you may need to remove this rule for those applications.

X-Powered-By

There are two ways to do remove this header as well. Second method would be the preferred one.

1. Using IIS HTTP Response headers.

Open the site which you would like to open and then click on the HTTP Response Headers option.

Click on the X-Powered-By header and then click Remove on the Actions Pane to remove it from the response.

2. Using URLRewite Rule.

Please note that it will not remove the header all together but it will remove the value of it.

Step 1. Install URLRewrite. To install the URLRewrite please go to the following link

Step 2. Open the site on which you would like to remove the X-Powered-By header and Click on the URLRewrite section.

Step 3. Click on the “View Server Variables” in the Actions pane in the right hand side.

Step 4. Click on the Add button and then enter “RESPONSE_X-POWERED-BY” in the textbox provided.

Step 5. Now we need to create an outbound rule. To know how to create an outbound rule, look at the following link

http://www.iis.net/learn/extensions/url-rewrite-module/creating-outbound-rules-for-url-rewrite-modul...

Step 6. Create an Outbound rule as the following

Please note that this is a website-specific rule. If you want to create the rule for all of your applications, create the rule at the server level. Also, some applications, especially third party applications, may require the x-powered-by header, so you may need to remove this rule for those applications.

X-AspNet-Version

There are two ways to do remove this header as well. Preferred one is the first one.

1. Using the httpRuntime element.

Add the following line in your web.config in the <system. Web> section

2. Using an URLRewite rule.

Please note that it will not remove the header all together but it will remove the value of it.

Step 1. Install URLRewrite. To install the URLRewrite please go to the following link

Step 2. Open the site on which you would like to remove the Server header and go to the URLRewrite section.

Step 3. Click on the “View Server Variables” in the Actions pane in the right hand side.Step 4. Click on the Add button and then enter “RESPONSE_X-ASPNET-VERSION” in the textbox provided.

Step 5. Now we need to create an outbound rule. To know how to create an outbound rule, look at the following link

http://www.iis.net/learn/extensions/url-rewrite-module/creating-outbound-rules-for-url-rewrite-modul...

Step 6. Create an Outbound rule as the following.

Please note that this is a website-specific rule. If you want to create the rule for all of your applications, create the rule at the server level. Also, some applications, especially third party applications, may require the x-aspnet-version header, so you may need to remove this rule for those applications.

Author: Mathur Varun (MSFT)

Tech Reviewed by: Enamul Khaleque (MSFT)

Occasional Visitor

I tried by setting the registry key of Disable HTTP Header to 1. But the server name was coming in response. I then changed the registry key to 2 and then the issues was fixed and server name was not coming in response.

Microsoft

@Sujitha0212 This method works only when the Server header comes as “Microsoft-HTTPAPI/2.0”. It takes value 0 (don't disable server header) or non-zero(disable server header). 1 or 2 or any value greater than zero should have the same affect. It's quite strange why a value of 2 worked but 1 did not. Thanks for sharing the info!

Regular Visitor

Well, in the "Internet Information Services" - management console I switched to "HTTP Response Headers" and added "Server"-Value "Webserver" which overrides the "Microsoft-IIS/10.0" with "Webserver".

That easy...

EDIT: or you add this manually (caution!) to C:\Windows\System32\inetsrv\config\applicationHost.config

...
<httpProtocol>
<clear />
</httpProtocol>
</system.webServer>
...

Regular Visitor

And, you could do this per web-app within the web.config file:

<configuration>
<system.webServer>
<httpProtocol>
<clear/>
</httpProtocol>
</system.webServer>
</configuration>

Frequent Visitor

it works fine on 200 status code
on 400 error, server header shows "Microsoft-HTTPAPI/2.0"
on 404 error, server header still shows "Microsoft-IIS/8.5"
on 200, server header shows "Unknown" as per my value in rewrite module.
my registry entry is DisableServerHeader = 1
why it is not working? I am using windows server 2012 R2 with IIS 8.5