[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Paul Vasicek updated TS-469: - Attachment: APIMAN-1273.patch This works on ATS 4x 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: sometime Attachments: APIMAN-1273.patch 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.3.4#6332)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-469: -- Assignee: (was: Bryan Call) 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: sometime 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.3.4#6332)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-469: -- Fix Version/s: (was: 5.2.0) sometime 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: sometime 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.3.4#6332)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-469: - Assignee: Bryan Call 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 Assignee: Bryan Call 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)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ 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)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ https://issues.apache.org/jira/browse/TS-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-469: - Labels: CoAdvisor (was: ) 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. (Originally discovered with Coadvisor). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ 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: (was: 6.0.0) 5.0.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.1.6 Reporter: Leif Hedstrom Assignee: Bryan Call Labels: CoAdvisor Fix For: 5.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)
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ 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: (was: 3.3.3) 3.5.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.1.6 Reporter: Leif Hedstrom Fix For: 3.5.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. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ 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: (was: 3.1.1) 3.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.1.6 Reporter: Leif Hedstrom Fix For: 3.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. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-469) A PUT request should invalidate a previously cached object with the same URI
[ 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
[ 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.
