intrigeri:
> Giorgio Maone wrote (13 Feb 2016 13:23:00 GMT) :
>> Whenever a page matching the pattern for a possible UI page (i.e.
>> "https://tails.boum.org/*"), DAVE currently fetches the IDF. This is
>> basically the only way to fix https://labs.riseup.net/code/issues/10685,
>> as noted in https://labs.riseup.net/code/issues/10685#note-5
>
>> Of course you can and should limit the actual network activity by
>> properly using Chache-Control and/or ETag headers.
>
> By the way, did you IA+DAVE folks already check if the server-side
> Cache-Control / ETag settings are OK for the IDF? (I vaguely remember
> sajolida noticing weird stats in the access logs, that might be caused
> by suboptimal HTTP server settings.)
I know that I haven't requested anything special to root@??? for
this file and the stats I got look like it's not cached properly.
But I don't know much about these things myself. Here is a full HTTP
request.
Should we add "Cache-Control" and "ETag", and remove "Expires"?
$ wget --server-response
https://tails.boum.org/install/v1/Tails/i386/stable/latest.yml
--2016-03-29 18:06:06--
https://tails.boum.org/install/v1/Tails/i386/stable/latest.yml
Resolving tails.boum.org (tails.boum.org)... 204.13.164.188
Connecting to tails.boum.org (tails.boum.org)|204.13.164.188|:443...
connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
Date: Tue, 29 Mar 2016 18:06:08 GMT
Server: Apache/2.2.22 (Debian)
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
Strict-Transport-Security: max-age=15768000
Last-Modified: Fri, 18 Mar 2016 20:43:59 GMT
Accept-Ranges: bytes
Content-Length: 269
Cache-Control: max-age=0
Expires: Tue, 29 Mar 2016 18:06:08 GMT
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/plain
Content-Language: en
Length: 269 [text/plain]
Saving to: ‘latest.yml’
latest.yml
100%[==================================================================>]
269 --.-KB/s in 0s
2016-03-29 18:06:09 (2.59 MB/s) - ‘latest.yml’ saved [269/269]
