Changes between Version 2 and Version 3 of Ticket #1015, comment 1
- Timestamp:
- 14.10.2016 03:54:59 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1015, comment 1
v2 v3 1 1 Note that for static resources the browser cache //is// leveraged already by the means of the `Last-Modified` response header and conditional requests (`If-Modified-Since` request header). That is requests are possibly answered with 304 Not Modified. So, your one big js file will //not// be transferred with every request. Please check this. 2 2 3 Yes, by setting a `max-age` value in the `Cache-Control` response header we could avoid sending the request in the first place. But I think setting a`max-age=600` for just //all// static resources is not a good idea as this would destroy e.g. the save-reload turnaround while development (which relies on max-age=0). So we need further conceptualization here.3 Yes, by setting a `max-age` value in the `Cache-Control` response header we could avoid sending the request in the first place. But I think setting `max-age=600` for just //all// static resources is not a good idea as this would destroy e.g. the save-reload turnaround while development (which relies on max-age=0). So we need further conceptualization here. 4 4 5 5 What about this:
