[
https://issues.apache.org/jira/browse/TS-5098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig B updated TS-5098:
------------------------
Description:
On HEAD as of 16DEC2016 (102b66b9730780289ef71fa1ee33214cbcbcdde2)
When in Forward proxy mode, connecting to an HTTPS site, where the destination
site responds with TCP RESET, Traffic Server will restart due to Sig 11:
Segmentation fault.
If the upstream site instead silently drops the response, ATS will successfully
proceed with 502 (Tunnel Connection Failed).
No proxy chaining involved, direct: client -> ATS -> destination.
Test machine: Debian Jessie (8.6) x86_64
To replicate, make an HTTPS request - via ATS in forward-proxy-mode - to a
local (non-firewalled) server, with nothing running on TCP/443.
Watch manager.log for near immediate "[LocalManager::pollMgmtProcessServer]
Server Process terminated due to Sig 11: Segmentation fault" followed by
"[Alarms::signalAlarm] Server Process was reset"
was:
On HEAD as of 16DEC2016 (102b66b9730780289ef71fa1ee33214cbcbcdde2)
When in Forward proxy mode, connecting to an HTTPS site, where the destination
site responds with TCP RESET, Traffic Server will restart due to Sig 11:
Segmentation fault.
If the upstream site instead silently drops the response, ATS will successfully
proceed with 502 (Tunnel Connection Failed).
No proxy chaining involved, direct: client -> ATS -> destination.
To replicate, make an HTTPS request - via ATS in forward-proxy-mode - to a
local (non-firewalled) server, with nothing running on TCP/443.
Watch manager.log for near immediate "[LocalManager::pollMgmtProcessServer]
Server Process terminated due to Sig 11: Segmentation fault" followed by
"[Alarms::signalAlarm] Server Process was reset"
> Sig 11: Segmentation fault on TLS when destination server issues Reset
> ----------------------------------------------------------------------
>
> Key: TS-5098
> URL: https://issues.apache.org/jira/browse/TS-5098
> Project: Traffic Server
> Issue Type: Bug
> Components: TLS
> Reporter: Craig B
>
> On HEAD as of 16DEC2016 (102b66b9730780289ef71fa1ee33214cbcbcdde2)
> When in Forward proxy mode, connecting to an HTTPS site, where the
> destination site responds with TCP RESET, Traffic Server will restart due to
> Sig 11: Segmentation fault.
> If the upstream site instead silently drops the response, ATS will
> successfully proceed with 502 (Tunnel Connection Failed).
> No proxy chaining involved, direct: client -> ATS -> destination.
> Test machine: Debian Jessie (8.6) x86_64
> To replicate, make an HTTPS request - via ATS in forward-proxy-mode - to a
> local (non-firewalled) server, with nothing running on TCP/443.
> Watch manager.log for near immediate "[LocalManager::pollMgmtProcessServer]
> Server Process terminated due to Sig 11: Segmentation fault" followed by
> "[Alarms::signalAlarm] Server Process was reset"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
