Thanks bmartino1, but no, it doesn't have anything to do with Apache or running a program. This is how HFS identifies itself when someone get/download a file from our server. This is also being called as Server Signature (similar to browser's User Agent). This is a HTTP header value.
When some does a HTTP request to a file, HFS identifies itself as:
The same way, Apache server identifies itself as:
You may wonder why you may want to change this? The answer is simple: "just for fun" or "to protect our server" (since each version -of almost any server- has some deficiencies that could be exploited, and a hacker who knows your version number may benefit from it by focused attacks). You may read about this here (they talk there about Apache in that article, but the "server signature" also exist on HFS, and on almost every server).
You can test any Server Signature here: http://security.firewallmonitor.org/
Well, I expect mars/rejetto/silentplz/raybob have an answer for this, I mean a macro to change this value (or any other HTTP header value).
When some does a HTTP request to a file, HFS identifies itself as:
Code: [Select]
Server: HFS 2.3hThe same way, Apache server identifies itself as:
Code: [Select]
Server: Apache/2.2.17 (Win32) PHP/5.2.17You may wonder why you may want to change this? The answer is simple: "just for fun" or "to protect our server" (since each version -of almost any server- has some deficiencies that could be exploited, and a hacker who knows your version number may benefit from it by focused attacks). You may read about this here (they talk there about Apache in that article, but the "server signature" also exist on HFS, and on almost every server).
You can test any Server Signature here: http://security.firewallmonitor.org/
Well, I expect mars/rejetto/silentplz/raybob have an answer for this, I mean a macro to change this value (or any other HTTP header value).
Logged