trafficserver-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eagen, Dave" <David.Ea...@biworldwide.com>
Subject RE: HTTP 502 for SSL connections
Date Thu, 03 Feb 2011 17:07:32 GMT
We're running 2.1.5-unstable and OpenSSL 0.9.8e. 

-----Original Message-----
From: Igor Galić [mailto:i.galic@brainsware.org] 
Sent: Thursday, February 03, 2011 10:57 AM
To: users@trafficserver.apache.org
Subject: Re: HTTP 502 for SSL connections


----- "Dave Eagen" <David.Eagen@biworldwide.com> wrote:

> We are trying out Traffic Server and have run into a problem with SSL

Which version of ATS are you running, which version of OpenSSL?

> connections made through it. Most of the time the connections work 
> fine (HTTP 200) but sometimes an HTTP 502 is reported. This is 
> happening on requests to the same destination URL.
> 
> If instead of running Traffic Server we run Squid (on the same 
> physical machine) we never get the 502 errors. We have confirmed that 
> the 502's did not happen because of actual connectivity problems with 
> the site we are attempting to access.
> 
> Where can I start looking to figure out why these 502's are happening 
> with Traffic Server but not Squid?
> 
> Failure example logs:
> 
> 
> Error example:
> 
> (squid.blog)
> 
> 1296576007.087 58 1.2.3.4 ERR_CONNECT_FAIL/502 454 CONNECT 
> xxx.yyy.com:443/ - DIRECT/xxx.yyy.com text/html -
> 
> (error.log)
> 
> 20110201.10h00m07s RESPONSE: sent 1.2.3.4 status 502 (Tunnel 
> Connection Failed) for 'xxx.yyy.com:443/'
> 
> 
> 
> Success example:
> 
> (squid.blog)
> 
> 1296576041.850 116107 1.2.3.4 TCP_MISS/200 103 CONNECT 
> xxx.yyy.com:443/ - DIRECT/xxx.yyy.com - -
> 
> 
> 
> 
> 
> -Dave

i

--
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.galic@brainsware.org
URL: http://brainsware.org/

This e-mail message is being sent solely for use by the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.
 If you are not the intended recipient, please contact the sender by phone or reply by e-mail,
delete the original message and destroy all copies. Thank you.

Mime
View raw message