[ https://issues.apache.org/jira/browse/TS-3343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298985#comment-14298985 ]
ASF subversion and git services commented on TS-3343: ----------------------------------------------------- Commit e5ac376b91ef2ac5aff4c87d0b33f9d3c6aa0637 in trafficserver's branch refs/heads/master from [~wbardwel] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=e5ac376 ] TS-3343 outbound transparent can end up with Connection: keep-alive headers on failures Revised to check for NULL ua_session and restrict new behavior to specific status codes. > 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)