| From | Sent On | Attachments |
|---|---|---|
| Simon Leins | Dec 21, 2010 1:36 pm | |
| Eugaia | Dec 21, 2010 2:24 pm | |
| António P. P. Almeida | Dec 21, 2010 2:38 pm | |
| Simon Leins | Dec 21, 2010 2:48 pm | |
| Dennis Jacobfeuerborn | Dec 21, 2010 4:16 pm | |
| Simon Leins | Dec 22, 2010 12:36 am |
| Subject: | Server signature | |
|---|---|---|
| From: | Simon Leins (simo...@gmail.com) | |
| Date: | Dec 21, 2010 1:36:59 pm | |
| List: | ru.sysoev.nginx | |
Hi all,
We are working on a project for a customer.
For political reasons, the customer will refuse to have any non-IIS web servers. Since we deliver the service as SaaS, the customer can only see the OS fingerprint and server signature (together with a few other things like error pages).
For the OS signature we are able to change it on the fly with a security/network appliance and make it looks unknown, but we now need to fake the web server signature. Rather than adding a proxy such as varnish in front, I am looking for the way to directly patch the source code to change the server signature.
Could someone point me the file name to patch to get this done?
As for curious, I work behind the scene so the end-user does not know my name :-)
Thanks!
Regards,
-- Simon
_______________________________________________ nginx mailing list ngi...@nginx.org http://nginx.org/mailman/listinfo/nginx





