[jira] [Updated] (TS-2916) combo_handler does not set the response headers properly

2014-08-01 Thread Alan M. Carroll (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alan M. Carroll updated TS-2916:


Fix Version/s: (was: 5.1.0)
   5.2.0

 combo_handler does not set the response headers properly
 

 Key: TS-2916
 URL: https://issues.apache.org/jira/browse/TS-2916
 Project: Traffic Server
  Issue Type: Bug
  Components: Plugins
Reporter: Feifei Cai
Assignee: Kit Chan
  Labels: review, yahoo
 Fix For: 5.2.0

 Attachments: TS-2916.diff


 # Cache-Control: max-age=xxx
 combo_handler plugin should parse each url's max-age value in Cache-Control 
 header, and use the minimal value in the response header. The hard-code 10 
 years max-age prevents cache from refresh, even though we have parsed the 
 value in Expires headers.
 See 
 [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]:
 If a response includes both an Expires header and a max-age directive, the 
 max-age directive overrides the Expires header, even if the Expires header is 
 more restrictive.
 # Duplicated headers
 We add support for whitelist of headers in a recent 
 [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8]
 When we have added headers specified in whitelist, we need to check for 
 duplicated headers in the following response write actions.
 # Multiple values
 Some headers has multiple values, e.g. Cache-Control: max-age=3600, public. 
 It has 2 values: max-age=3600 and public.
 We need to parse all the values for each header specified in whitelist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (TS-2916) combo_handler does not set the response headers properly

2014-07-04 Thread Feifei Cai (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feifei Cai updated TS-2916:
---

Labels: yahoo  (was: )

 combo_handler does not set the response headers properly
 

 Key: TS-2916
 URL: https://issues.apache.org/jira/browse/TS-2916
 Project: Traffic Server
  Issue Type: Bug
  Components: Plugins
Reporter: Feifei Cai
  Labels: yahoo

 # Cache-Control: max-age=xxx
 combo_handler plugin should parse each url's max-age value in Cache-Control 
 header, and use the minimal value in the response header. The hard-code 10 
 years max-age prevents cache from refresh, even though we have parsed the 
 value in Expires headers.
 See 
 [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]:
 If a response includes both an Expires header and a max-age directive, the 
 max-age directive overrides the Expires header, even if the Expires header is 
 more restrictive.
 # Duplicated headers
 We add support for whitelist of headers in a recent 
 [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8]
 When we have added headers specified in whitelist, we need to check for 
 duplicated headers in the following response write actions.
 # Multiple values
 Some headers has multiple values, e.g. Cache-Control: max-age=3600, public. 
 It has 2 values: max-age=3600 and public.
 We need to parse all the values for each header specified in whitelist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Updated] (TS-2916) combo_handler does not set the response headers properly

2014-07-04 Thread Feifei Cai (JIRA)

 [ 
https://issues.apache.org/jira/browse/TS-2916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Feifei Cai updated TS-2916:
---

Attachment: TS-2916.diff

 combo_handler does not set the response headers properly
 

 Key: TS-2916
 URL: https://issues.apache.org/jira/browse/TS-2916
 Project: Traffic Server
  Issue Type: Bug
  Components: Plugins
Reporter: Feifei Cai
  Labels: yahoo
 Attachments: TS-2916.diff


 # Cache-Control: max-age=xxx
 combo_handler plugin should parse each url's max-age value in Cache-Control 
 header, and use the minimal value in the response header. The hard-code 10 
 years max-age prevents cache from refresh, even though we have parsed the 
 value in Expires headers.
 See 
 [rfc2616-sec14.9.3|http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3]:
 If a response includes both an Expires header and a max-age directive, the 
 max-age directive overrides the Expires header, even if the Expires header is 
 more restrictive.
 # Duplicated headers
 We add support for whitelist of headers in a recent 
 [commit|https://github.com/apache/trafficserver/commit/f61b1b416f4bb99854c6b6c77b12f742b5af9ca8]
 When we have added headers specified in whitelist, we need to check for 
 duplicated headers in the following response write actions.
 # Multiple values
 Some headers has multiple values, e.g. Cache-Control: max-age=3600, public. 
 It has 2 values: max-age=3600 and public.
 We need to parse all the values for each header specified in whitelist.



--
This message was sent by Atlassian JIRA
(v6.2#6252)