I should have been more precise. The browser will cache the static files
and re-use them, but it will still send requests to the server to check
whether the cached version has expired (if not expired, the server will
send a 304 response indicating the cached version is still current, so the
entire file will not be re-sent). This assumes you are using web2py to
serve the static files (as opposed to configuring your web server to do so
directly).
Anthony
On Friday, July 18, 2014 10:56:41 AM UTC-4, Niphlod wrote:
>
>
>>>
>> The browser will cache your static files. No need to cache on the server,
>> as they are not generated dynamically.
>>
>>
>>
> sadly it won't. For a debatable design decision, static files are not
> served with cache headers.
> the correct way to enable "far in the future cache headers" and avoid
> multiple 304s is to use static versioning, i.e.
>
> URL('static', '_1.2.3/images/image1.jpg')
>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
