-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assets are not cached #368
Comments
Are you using non cache digested versions of the assets? Because that was a On Aug 4, 2016 7:16 PM, "jako512" [email protected] wrote:
|
I'm using assets with cache digest. |
can you send me a screen shot and sample header please? |
Version 2.8.0 + PR#365:
Version 2.10.1:
|
Thank you! are you routing this through nginx direct to tomcat or using storagePath copy?
|
Direct nginx -> jetty |
Issue still confirmed on 2.11.0 |
Id try a newer version and also @majkelo send an example. If the asset is not using a cache digest name it does a no-cache which doesn't mean its not being cached it means its asking the server to validate its ETag header properly |
I've included plugin inline and manually updated asset-pipeline-core to 2.11.2 (just like in #378 but without any changes in AssetPipelineFilter.groovy ) and it seems it's working! btw I'm not sure about https://github.com/bertramdev/asset-pipeline/blob/d51380f5c3847e695cd81cbc9991aecba7a1ea9e/asset-pipeline-core/src/main/groovy/asset/pipeline/AssetPipelineResponseBuilder.groovy#L63 I already have:
|
I just noticed this on Grails 3.2.11 with asset-pipeline-grails:2.14.1 when I ran a standalone jar with prod environment. My varnish server refused to cache images because of this. This happen with images and other kind blobs like fonts. Javascript and CSS works correctly. |
Since version 2.9.0 assets are served with HTTP header
Cache-Control: no-cache
in production.The text was updated successfully, but these errors were encountered: