You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/09/28 01:50:37 UTC
[jira] Created: (TS-469) A PUT request should invalidate a
previously cached object with the same URI
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
Reporter: Leif Hedstrom
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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TS-469) A PUT request should invalidate a
previously cached object with the same URI
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915600#action_12915600 ]
Leif Hedstrom commented on TS-469:
----------------------------------
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.
> 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.3.0
> Reporter: Leif Hedstrom
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-469) A PUT request should invalidate a
previously cached object with the same URI
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-469:
-----------------------------
The same with a POST request.
> 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.3.0
> Reporter: Leif Hedstrom
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-469) A PUT request should invalidate a
previously cached object with the same URI
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-469:
-----------------------------
Affects Version/s: 2.3.0
> 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.3.0
> Reporter: Leif Hedstrom
>
> 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).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TS-469) A PUT request should invalidate a
previously cached object with the same URI
Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-469:
-----------------------------
Fix Version/s: 2.3.0
> 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.3.0
> Reporter: Leif Hedstrom
> Fix For: 2.3.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.
> (Originally discovered with Coadvisor).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.