Some of the response headers we are sending to clients serve no actual purpose and we could strip them out at the frontend layer.
| Header | Example |
|--|--
| X-Powered-By | HHVM/3.18.6-dev || Status
| X-Varnish | 521726689 533337780, 225083667 220092282, 525815818 515121340 ||--|--|--
| X-Powered-By | PHP/7.2.26-1+0~20191218.33+debian9~1.gbpb5a340+wmf1|
| X-Varnish | 521726689 533337780, 225083667 220092282, 525815818 515121340|
| Server | mw1238.eqiad.wmnet ||
| ~~Via~~| ~~1.1 varnish (Varnish/5.1), 1.1 varnish (Varnish/5.1), 1.1 varnish (Varnish/5.1)~~| {icon check} Removed
| ~~Via~~ {icon check} | ~~1.1 varnish (Varnish/5.1), 1.1 varnish (Varnish/5.1), 1.1 varnish (Varnish/5.1)~~ |X-Analytics~~ |~~https=1;nocookies=1~~ | {icon check} Removed
In the specific case of cache_upload, there are a few headers set by swift which we might also consider removing:
| Header | Example |
|--|--
|X-Object-Meta-Sha1Base36 | iui1kxpdsmxapvmrdyhn5vaxn2il53x |
| X-Timestamp | 1487337414.04422 |
| X-Trans-Id | tx75bd096fde6d4999bf946-005afabc1f |
See also:
* {T110353}