[jira] [Updated] (TS-3342) Non-standard method in bad request can cause crash

2015-03-08 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-3342:
--
Labels: review  (was: )

 Non-standard method in bad request can cause crash
 --

 Key: TS-3342
 URL: https://issues.apache.org/jira/browse/TS-3342
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: William Bardwell
Assignee: William Bardwell
  Labels: review
 Fix For: 5.3.0

 Attachments: TS-3342.diff


 Fix is to check for a normal sort of method (that would actually need a cache 
 lookup) in HttpTransact::HandleCacheOpenReadMiss() to do
 {code}
  s-cache_info.action = CACHE_DO_NO_ACTION;
 {code}
 instead of
 {code}
  s-cache_info.action = CACHE_PREPARE_TO_WRITE;
 {code}
 for anything weird.  But I am concerned that this might cause problems if 
 someone wants to add support for a weird method...but maybe that never works 
 right with the cache anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (TS-3342) Non-standard method in bad request can cause crash

2015-01-29 Thread William Bardwell (JIRA)

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

William Bardwell updated TS-3342:
-
Attachment: TS-3342.diff

Patch, but lists the 'methods that effect the cache' is that list totally known?

 Non-standard method in bad request can cause crash
 --

 Key: TS-3342
 URL: https://issues.apache.org/jira/browse/TS-3342
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: William Bardwell
 Attachments: TS-3342.diff


 Fix is to check for a normal sort of method (that would actually need a cache 
 lookup) in HttpTransact::HandleCacheOpenReadMiss() to do
 {code}
  s-cache_info.action = CACHE_DO_NO_ACTION;
 {code}
 instead of
 {code}
  s-cache_info.action = CACHE_PREPARE_TO_WRITE;
 {code}
 for anything weird.  But I am concerned that this might cause problems if 
 someone wants to add support for a weird method...but maybe that never works 
 right with the cache anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (TS-3342) Non-standard method in bad request can cause crash

2015-01-29 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-3342:
--
Assignee: William Bardwell  (was: Leif Hedstrom)

 Non-standard method in bad request can cause crash
 --

 Key: TS-3342
 URL: https://issues.apache.org/jira/browse/TS-3342
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: William Bardwell
Assignee: William Bardwell
 Fix For: 5.3.0

 Attachments: TS-3342.diff


 Fix is to check for a normal sort of method (that would actually need a cache 
 lookup) in HttpTransact::HandleCacheOpenReadMiss() to do
 {code}
  s-cache_info.action = CACHE_DO_NO_ACTION;
 {code}
 instead of
 {code}
  s-cache_info.action = CACHE_PREPARE_TO_WRITE;
 {code}
 for anything weird.  But I am concerned that this might cause problems if 
 someone wants to add support for a weird method...but maybe that never works 
 right with the cache anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (TS-3342) Non-standard method in bad request can cause crash

2015-01-29 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-3342:
--
Fix Version/s: 5.3.0

 Non-standard method in bad request can cause crash
 --

 Key: TS-3342
 URL: https://issues.apache.org/jira/browse/TS-3342
 Project: Traffic Server
  Issue Type: Bug
  Components: Core
Reporter: William Bardwell
 Fix For: 5.3.0

 Attachments: TS-3342.diff


 Fix is to check for a normal sort of method (that would actually need a cache 
 lookup) in HttpTransact::HandleCacheOpenReadMiss() to do
 {code}
  s-cache_info.action = CACHE_DO_NO_ACTION;
 {code}
 instead of
 {code}
  s-cache_info.action = CACHE_PREPARE_TO_WRITE;
 {code}
 for anything weird.  But I am concerned that this might cause problems if 
 someone wants to add support for a weird method...but maybe that never works 
 right with the cache anyway...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)