Feature #9023: Document how to disable ETag on common servers

Feature #9023

Document how to disable ETag on common servers

Added by sajolida 2015-03-06 19:19:45 . Updated 2015-08-03 07:50:10 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Infrastructure

Target version:

Tails_1.5

Start date:

2015-03-06

Due date:

% Done:

100%

Feature Branch:

doc/9023-disable-etag

Type of work:

Contributors documentation

Blueprint:

Starter:

Affected tool:

Deliverable for:

Description

We could start with Apache and nginx

Subtasks

History

#1 Updated by sajolida 2015-03-06 19:24:30

Subject changed from Investigate how to disable ETag with common servers to Document how to disable ETag on common servers
Type of work changed from Code to Contributors documentation

#2 Updated by sajolida 2015-03-06 19:25:08

blocks ~~Feature #9024~~: Ask mirror operators to disable ETag added

#3 Updated by intrigeri 2015-03-06 19:56:28

sajolida wrote:
> We could start with Apache and nginx

If we’re going to test this with check-mirrors (which is apparently the case with ~~Feature #9025~~), then we should maybe do that for all web servers we document on https://tails.boum.org/contribute/how/mirror/ (Apache, nginx, lighttpd).

#4 Updated by sajolida 2015-07-12 03:24:25

Assignee set to sajolida

First results: * Apache

FileETag None

https://httpd.apache.org/docs/2.2/mod/core.html#fileetag

Nginx
- etag off
- http://nginx.org/en/docs/http/ngx_http_core_module.html#etag
lighttpd
- static-file.etags = "enable"
- http://redmine.lighttpd.net/projects/1/wiki/docs_configurationoptions#Lighttpd-Core

This can be test with wget --server-response.

Still, I won’t document this before writing to mirror operators. I’d rather ask them to fix the contribute documentation after testing and deploying such changes. I have no easy access to a web server, and they do.