Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

*** The wcm.io Project is closing down this JIRA Instance in favor of GitHub issues. *** Please use the corresponding GitHub projects to report issues - or the mailing list for general discussion.

Issues

Go to all issues
Select view

Select search mode

 
2 of 2

DAM AssetService Dataversion is cached on Dispatcher

Fixed

Description

If a Dataversion from the DAM AssetService is requested through a dispatcher, all further requests can return a wrong version as the dispatcher returns a cached reply.
Imho Dataversion call should never be cached (e.g. through Header "Dispatcher": "no-cache")

Gliffy Diagrams

Details

Assignee

Reporter

Components

Fix versions

Priority

Created December 10, 2015 at 9:00 AM
Updated December 16, 2015 at 5:52 PM
Resolved December 11, 2015 at 11:56 AM
Configure

Activity

Show:

Stefan SeifertDecember 16, 2015 at 5:52 PM

release 1.2.0 is on maven central

Alexander MuthmannDecember 11, 2015 at 1:04 PM

Any chance for a release next week? We'd love to include this.

Stefan SeifertDecember 11, 2015 at 11:56 AM

thanks, i've merged it and updated the unit test

Alexander MuthmannDecember 11, 2015 at 11:47 AM

Stefan SeifertDecember 11, 2015 at 11:32 AM

makes sense definitely.

probably we disable caching not only for dispatcher, but for other downstream proxies as well, e.g. via http://wcm.io/wcm/commons/apidocs/io/wcm/wcm/commons/caching/CacheHeader.html#setNonCachingHeaders-javax.servlet.http.HttpServletResponse-