3 ms·
Sounds nice, though this one restriction: Do not rely on query string parameters. CloudFront does not preserve query string parameters. (For more informat
by pquerna 16y ago
Sounds nice, though this one restriction:
Do not rely on query string parameters. CloudFront does not
preserve query string parameters. (For more information,
see Query String Parameters.)
Kinda sucks :(
Makes it a not-quite-standard http reverse proxy. We have been putting cache versioning in our query strings, just because it was easier in our framework than changing the base url... but guess we should just fix that.
- chunkbot 16y agoYou should use an ETag in your HTTP request header to do versioning, and keep the URL static.
- pquerna 16y agoNo. The better way is to change the URL -- then you setup your ETags + Cache-Control so that the object never expires, ever. See Also: http://public.yahoo.com/bfrance/radwin/talks/http-caching-apachecon2004.htm http://public.yahoo.com/bfrance/radwin/talks/http-caching-ap... http://journal.paul.querna.org/articles/2007/06/06/mod_never_expire/ http://journal.paul.querna.org/articles/2007/06/06/mod_never...
- al_james 16y agoI am going to cope with this using an apache rewrite. E.g. /resources/screen_ver<any code>.css -> /resources/screen.css Should be simple to remove any _ver<any> string from the url via apache.