Solved: website js expire

ichwilldich12345 at gmx.de ichwilldich12345 at gmx.de
Sat Oct 28 11:56:49 UTC 2017


Sorry, I have overseen the year changed.
It was a browser issue, cache limit was set to 2mB, far too less. Now it works.
Thank you Tom

Am 28. Oktober 2017 12:57:04 MESZ schrieb Tom Hughes <tom at compton.nu>:
>On 28/10/17 10:35, ichwilldich12345 at gmx.de wrote:
>
>> When accessing any site at https://www.openstreetmap.org/ a large
>script 
>> of 1 mB is downloaded every time 
>>
>(https://www.openstreetmap.org/assets/application-4d6830b2c7fa16ab8de03c882e3944a391b238a843949ed694ba7d2a13aee639.js).
>> Currently the Expires header is set to the same as Date so it will
>not 
>> be cached for next access.
>> That results in long waiting times on mobile connections and 
>> unneccessary data consumptions at the servers.
>> This issue could be solved by extending expiry time to a few days or
>by 
>> using 304 not modified status code.
>
>Err, that exactly what we do. It has a one year expiry:
>
>bericote [~] % HEAD 
>https://www.openstreetmap.org/assets/application-4d6830b2c7fa16ab8de03c882e3944a391b238a843949ed694ba7d2a13aee639.js
>
>| fgrep Expires
>Expires: Sun, 28 Oct 2018 10:56:31 GMT
>
>Tom
>
>-- 
>Tom Hughes (tom at compton.nu)
>http://compton.nu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20171028/b688b11f/attachment.html>


More information about the rails-dev mailing list