We need a solution to inform browser of css changes so thad cached css will no longer be used.
Here are some solution described:
For me the Last-Modified header seems to be a better solution. But we can check if eTag works for generated css.
The last-modified header is an weak and outdated cache control mechanism.
It is often used only as fall back for the expires settings.
As far as I know you can add the etag header for generated resources too. It is just a hash you set in the header. And when this hash is the checksum for the generated content, then it only changes, when the content has changed. And then it’s done, isn’t it?
We get the css file using a jersey resource from mycore. Perhaps we should add the cache mechanism there:
… there is also a section about caching use etag