Can't remove Server: Apache header

Question

I have "Server: Apache" in my HTTP response headers and want to remove it. I followed instructions like adding this to httpd.conf:

ServerSignature Off   ServerTokens Prod Header unset Server 

But the last line has no effect. First two lines have changed header's content (earlier it contained also information about OS and PHP), but I need to remove it completely. How to do this?

Answer 1

Apache don't allow you to unset this completely. In fact some of the developers are vehemently against adding this despite it being a simple code change that's been suggested (and even written!) several times. See here and here for just some of the discussions where this has been brought up and rejected.

They give various reasons for this, including:

1. It might make it more difficult to count the number of Apache installs in the wild. This is, I suspect, the main reason. Web server usage is fiercely contested and one of Apache's rivals (which may or may not begin with an N) regularly posts how it is gaining ground on Apache and most scans will be based on the HTTP Header, so I can understand this reluctance to make it easier to hide this.

2. Security by obscurity is a myth, and gives a false sense of security as it's easy to fingerprint a server to see which software it likely is, based on how it responds to certain requests. While there is an inkling of truth in that, specifying ServerTokens as Full by default definitely is a security issue leaking far too much information than should be shown by default on a public website.

3. It may or may not be against the HTTP spec to not supply a server header. This seems to be in some disputes and still doesn't answer why they don't allow you to change it to some random string rather than Apache.

4. It makes it difficult to debug issues, but you'd think anyone needing to debug would know, or be able to find out, the exact versions.

5. Proxy servers "might" handle requests differently if they know the server type at the other end. Which is wrong of proxy servers IMHO and I doubt it's done much anymore.

6. If people really want to amend or hide this header they can edit the source code. Which is, quite frankly, a dangerous recommendation to advise people with no experience of the code to do and could lead to other security issues if they run from a non-packaged version just to add this.

They even goes as far as adding this in the official documentation:

Setting ServerTokens to less than minimal is not recommended because it makes it more difficult to debug interoperational problems. Also note that disabling the Server: header does nothing at all to make your server more secure. The idea of "security through obscurity" is a myth and leads to a false sense of safety.

That reasoning is, IMHO, ridiculous and, as I say, if that's the main reason to not allow it then I don't see why they don't change their stance. At worse case it doesn't add anything as they say and it stops this whole question being raised every so often though personally I think the less unnecessary information you give out, the better so would prefer to be able to turn this off.

Until that unlikely u-turn, you're left with:

1. Setting it minimal (so it will show "Apache") - which is probably good enough
2. Editing the source code - which is overkill except for the most paranoid, and means the same change needs to be applied on each new version.
3. Installing ModSecurity - which (at least used to) allow you to overwrite (but not remove) this header to whatever you wanted to hide the server software. Probably overkill to install this just for that, though there are other benefits to a WAF.
4. Proxy Apache behind another web server which allows you to change this field.
5. Switch to another web server.

It should be noted however, for points 4 and 5, that most other web servers don't allow you to turn this off either so this is not a problem unique to Apache. For example Nginx doesn't allow this to be turned off without similarly editing the source code.

Answer 2

Header retrieval

To get the headers, this seems to work adequately if on the server (all tests done on Ubuntu 14.04 Trusty Tahr):

curl -v http://localhost:80/ | head 

which produces something like:

< HTTP/1.1 200 OK < Date: Mon, 25 Jan 2021 09:17:51 GMT * Server Apache/2.4.7 (Ubuntu) is not blacklisted < Server: Apache/2.4.7 (Ubuntu) 

Removing the version number

To remove the version number, edit the file /etc/apache2/conf-enabled/security.conf and amend the lines:

• ServerTokens OS to ServerTokens Prod
• ServerSignature On to ServerSignature Off

and restart Apache:

sudo service apache2 restart 

You should now get the a response like:

< HTTP/1.1 200 OK < Date: Mon, 25 Jan 2021 09:20:03 GMT * Server Apache is not blacklisted < Server: Apache 

Removing the word "Apache"

To remove the word Apache completely, first install ModSecurity:

sudo apt-get install libapache2-mod-security2 

The following lines appear to not be required (enabling the module and restarting Apache) but for reference:

sudo a2enmod security2 sudo service apache2 restart 

Check that the module is enabled:

apachectl -M | grep security 

which should show:

security2_module (shared) 

Then although you can amend /etc/modsecurity/modsecurity.conf (by renaming modsecurity.conf-recommended), instead amend /etc/apache2/apache.conf which seems easier (note you can use whatever name you want, in this case I've simply used a space):

<IfModule security2_module>     SecRuleEngine on     ServerTokens Min     SecServerSignature " " </IfModule>  

(Using Min rather than Full also prevents modules such as mod_fastcgi appearing after the blank server name.)

Then restart Apache:

sudo service apache2 restart 

Final check

Now when you run the command:

curl -v http://localhost:80/ | head 

you should get:

< HTTP/1.1 200 OK < Date: Mon, 25 Jan 2021 09:31:11 GMT * Server  is not blacklisted < Server: