You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
groovy.lang.MissingPropertyException: No such property: file for class: asset.pipeline.grails.AssetPipelineFilter
at asset.pipeline.grails.AssetPipelineFilter.hasNotChanged(AssetPipelineFilter.groovy:211)
at asset.pipeline.grails.AssetPipelineFilter.doFilter(AssetPipelineFilter.groovy:61)
In method asset.pipeline.grails.AssetPipelineFilter#hasNotChanged a file property is accessed in hasNotChanged = new Date(file?.lastModified()) <= sdf.parse(ifModifiedSince) which does not exist and it causes two issues: 1) most likely the caching logic does not work and 2) stacktraces get logged in tremendous amounts.
Applies to version 2.9.1. It seems the same problem is still present on master.
The text was updated successfully, but these errors were encountered:
sbearcsiro
added a commit
to sbearcsiro/grails-asset-pipeline
that referenced
this issue
Jan 9, 2017
- Give last modified date to AssetPipelineResponseBuilder
- Remove special last modified date handling from AssetPipelineFilter as AssetPipelineResponseBuilder handles it now
- Remove now unused methods hasNotChanged and getLastModifiedDate
sbearcsiro
added a commit
to sbearcsiro/grails-asset-pipeline
that referenced
this issue
Jan 9, 2017
- Give last modified date to AssetPipelineResponseBuilder
- Remove special last modified date handling from AssetPipelineFilter as AssetPipelineResponseBuilder handles it now
- Remove now unused methods hasNotChanged and getLastModifiedDate
In method
asset.pipeline.grails.AssetPipelineFilter#hasNotChanged
afile
property is accessed inhasNotChanged = new Date(file?.lastModified()) <= sdf.parse(ifModifiedSince)
which does not exist and it causes two issues: 1) most likely the caching logic does not work and 2) stacktraces get logged in tremendous amounts.Applies to version 2.9.1. It seems the same problem is still present on master.
The text was updated successfully, but these errors were encountered: