Re:Amazon CloudFront Support for Custom Origins
by al_james on Tuesday November 09, 2010 @06:09AM
(#1886080)
I 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.
Re:Amazon CloudFront Support for Custom Origins
by chunkbot on Tuesday November 09, 2010 @12:27AM
(#1885466)
You should use an ETag in your HTTP request header to do versioning, and keep the URL static.
Re:Amazon CloudFront Support for Custom Origins
by pquerna on Tuesday November 09, 2010 @02:22AM
(#1885703)
No.
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-ap...
http://journal.paul.querna.org/articles/2007/06/06/mod_never...
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.