[jira] [Updated] (TS-3343) Outbound transparent can end up with Connection: keep-alive headers on failures

2015-03-30 Thread Leif Hedstrom (JIRA)

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

Leif Hedstrom updated TS-3343:
--
Summary: Outbound transparent can end up with Connection: keep-alive 
headers on failures  (was: outbound transparent can end up with Connection: 
keep-alive headers on failures)

> Outbound transparent can end up with Connection: keep-alive headers on 
> failures
> ---
>
> Key: TS-3343
> URL: https://issues.apache.org/jira/browse/TS-3343
> Project: Traffic Server
>  Issue Type: Bug
>Reporter: William Bardwell
>Assignee: William Bardwell
> Fix For: 5.3.0
>
>
> 502/504 responses generated by ATS can still end up with "Connection: 
> keep-alive" headers even when outbound_transparent is on, and connection is 
> doomed.
> Also for us not allowing setting that flag from the plugin with 
> TSHttpTxnOutgoingTransparencySet() when not compiled with full TPROXY support 
> is too mean, since that flag does change behavior in a few places in useful 
> ways even when not doing tproxy stuff.



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


[jira] [Updated] (TS-3343) outbound transparent can end up with Connection: keep-alive headers on failures

2015-01-28 Thread William Bardwell (JIRA)

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

William Bardwell updated TS-3343:
-
Fix Version/s: 5.3.0

> outbound transparent can end up with Connection: keep-alive headers on 
> failures
> ---
>
> Key: TS-3343
> URL: https://issues.apache.org/jira/browse/TS-3343
> Project: Traffic Server
>  Issue Type: Bug
>Reporter: William Bardwell
>Assignee: William Bardwell
> Fix For: 5.3.0
>
>
> 502/504 responses generated by ATS can still end up with "Connection: 
> keep-alive" headers even when outbound_transparent is on, and connection is 
> doomed.
> Also for us not allowing setting that flag from the plugin with 
> TSHttpTxnOutgoingTransparencySet() when not compiled with full TPROXY support 
> is too mean, since that flag does change behavior in a few places in useful 
> ways even when not doing tproxy stuff.



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