Re: [Tails-dev] Dynamically changing ISO URL in DAVE

Delete this message

Reply to this message
Autor: intrigeri
Data:  
A: Giorgio Maone
CC: The Tails public development discussion list
Assumptes vells: Re: [Tails-dev] Dynamically changing ISO URL in DAVE
Assumpte: Re: [Tails-dev] Dynamically changing ISO URL in DAVE
Hi,

[sorry for the delay...]

Giorgio Maone wrote (13 Feb 2016 13:23:00 GMT) :
> On 13/02/2016 13:49, sajolida wrote:
>> intrigeri:
>>>> Beside that, I think the JSON should be fetched every time the UI page
>>>> is reloaded (of course obeying to server-side caching directives), just
>>>> like we currently do with the IDF.
>>> I'm afraid I don't know under which circumstances the UI page is
>>> reloaded, so I lack the background info to integrate this proposal
>>> into my mental representation of the problem.
>>>
>>> @sajolida + @Giorgio: is this done as part of the Installation
>>> Assistant or DAVE course of operation, or only due to external factors
>>> (e.g. the user manually reloading the page, or restarting their
>>> browser)?
>> I *think* that Giorgio is only referring to a possible manual refresh
>> from the user. Keep in mind that DAVE is supposed to follow up on
>> download in the background and a user coming back to the download page
>> after possibly closing the tab, or to survive a manual page refresh or
>> browser restart.
>>
> 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.


> The same should apply to mirrors, if you want to keep them
> up-to-date.


Thanks for clarifying! It totally makes sense to me, and I've updated
#11109 accordingly.

Cheers,
--
intrigeri