Web Application Performance: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
== HTTP headers == | == Cache == | ||
=== HTTP headers === | |||
* Cache-Control: max-age | * Cache-Control: max-age | ||
| Line 16: | Line 18: | ||
* Can't override the browser behaviour - once it's cached with an expiry time | * Can't override the browser behaviour - once it's cached with an expiry time | ||
=== Fingerprinting / hashing === | |||
* Gets around caching, effectively forces a new request by using a unique filename based on file contents | |||
Revision as of 16:07, 11 July 2023
Cache
HTTP headers
- Cache-Control: max-age
- ETag: Hash of file, don't download if unchanged (but beware of how this is calculated, e.g. Apache may use inodes by default which differ on load-balanced servers)
- Expires: Re-download after this
- Last-Modified
Most headers won't help on first visit.
Request headers (conditional GET request):
- If-Modified-Since: Date/time
- If-None-Match: Hash (ETag)
Problems:
- Can't override the browser behaviour - once it's cached with an expiry time
Fingerprinting / hashing
- Gets around caching, effectively forces a new request by using a unique filename based on file contents