Solved: website js expire

ichwilldich12345 at ichwilldich12345 at
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>:
>On 28/10/17 10:35, ichwilldich12345 at wrote:
>> When accessing any site at a large
>> of 1 mB is downloaded every time 
>> Currently the Expires header is set to the same as Date so it will
>> 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
>> using 304 not modified status code.
>Err, that exactly what we do. It has a one year expiry:
>bericote [~] % HEAD 
>| fgrep Expires
>Expires: Sun, 28 Oct 2018 10:56:31 GMT
>Tom Hughes (tom at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the rails-dev mailing list