https://issues.apache.org/bugzilla/show_bug.cgi?id=56162
--- Comment #8 from Sebb <[email protected]> --- (In reply to Matt Parker from comment #6) > (In reply to Sebb from comment #5) > > (In reply to Matt Parker from comment #4) > > > (In reply to Sebb from comment #2) > > > > Not sure I understand the use case. > > > > > > > > Surely if the PUT changes the target of the GET, the Etag should change? > > > > > > You're correct, the ETag value does change, and the CacheManager works > > > properly with respect to this. However, I then want to create a new GET > > > request specifically to retrieve the full entity, but I no longer have the > > > ability to do this once the CacheManager is there. > > > > That's the part I don't understand. > > Surely the next GET after the PUT won't return the cached entry? > > If it does, then perhaps CM - or the site - is faulty? > > Technically, both CM and the site are working properly. But CM's behavior is > too restrictive to allow me to do what I want. After the PUT, the 2xx > response from the site includes the updated ETag value. But should a PUT response be cached? That seems wrong. -- You are receiving this mail because: You are the assignee for the bug.
