[
https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-469:
-----------------------------
Description:
If the client first fetches an object with GET, and TS caches it, a subsequent
PUT request for the same URL should invalidate the cached object.
Update: This is a problem with PUT/POST when the response from the origin is a
201, and there is a Location: header. We then must also invalidate any cached
object for the URL which the Location header refers to
(Originally discovered with Coadvisor).
was:
If the client first fetches an object with GET, and TS caches it, a subsequent
PUT request for the same URL should invalidate the cached object.
(Originally discovered with Coadvisor).
> A PUT request should invalidate a previously cached object with the same URI
> ----------------------------------------------------------------------------
>
> Key: TS-469
> URL: https://issues.apache.org/jira/browse/TS-469
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 2.1.6
> Reporter: Leif Hedstrom
> Labels: CoAdvisor
> Fix For: 6.0.0
>
>
> If the client first fetches an object with GET, and TS caches it, a
> subsequent PUT request for the same URL should invalidate the cached object.
> Update: This is a problem with PUT/POST when the response from the origin is
> a 201, and there is a Location: header. We then must also invalidate any
> cached object for the URL which the Location header refers to
> (Originally discovered with Coadvisor).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
