Re: [Tails-dev] ISO verification

Delete this message

Reply to this message
Author: sajolida
Date:  
To: The Tails public development discussion list
Old-Topics: Re: [Tails-dev] ISO verification [Was: [RFC] UX for ISO verification + Tails Installer + full upgrades]
Subject: Re: [Tails-dev] ISO verification
sajolida:
> Giorgio Maone:
>> On 04/03/2015 19:46, sajolida wrote:
>>> I tried to interrupt a download of the ISO with Tor Browser and,
>>> indeed, it's not possible to continue it.
>>
>> This seems due to a misconfiguration of your mirrors setup.
>> Specifically, I've tried to manually resume an interrupted download from
>> Firefox's download manager, which should have theoretically worked
>> because the (initial) server (announcing itself as "Server: Apache")
>> sent an "Accept-Ranges: bytes" header.
>> Unfortunately when I sent the second request with "Range:
>> bytes=37053248-", the second server I was dispatched to announcing
>> itself as "Server: lighty") actually answered with
>>
>> HTTP/1.1 206 Partial Content
>> Content-Range: bytes 37053248-954132479/954132480
>> Content-Length:    917079232

>>
>> i.e. correctly resumed the download, but the brower refused to go on
>> because the first response (from Apache) carried an
>>
>> Etag: "7c08c-38dee800-50fcad82a1400"
>>
>> header, while the second one (from Lighttpd) had
>>
>> Etag: "1421032332"
>>
>> misrepresenting the payloads as two different entities.
>>
>> Now, the easiest solution seems to me preventing Etag headers from being
>> sent in the ISO download HTTP responses (who's gonna *cache* a 1GB
>> response anyway?).
>
> Thanks for investigating all this! I created a parent ticket to work on
> this, see #9022 and subtasks.


Following up on that old issues. Today I replaced the last mirrors that
still had ETag enabled in our pool. It's now 100% ETag free :)