[squid-users] TCP_TUNNEL_ABORTED/200?

Alex Rousskov rousskov at measurement-factory.com
Wed Aug 31 15:38:17 UTC 2016


On 08/31/2016 02:20 AM, Ralf Hildebrandt wrote:
> One of our users is trying to connect to somw windows remoteapps via
> out squid proxy.
> 
> Logging in does seem to work, but somewhere along the line, the user
> is getting error messages. In our logs we're seeing the encrypted
> traffic (TCP_TUNNEL/200 CONNECT remoteapps.eortc.be:443), but then
> we're getting "TCP_TUNNEL_ABORTED/200" messages
> 
> I can't find anything on what exactly would cause a
> "TCP_TUNNEL_ABORTED/200"

In addition to what Amos has said, Squid bugs cause extra _ABORTED
suffixes in recent (but not recent enough) code. Two of such bugs were
fixed in trunk:

> revno: 14806
> branch nick: trunk
> timestamp: Wed 2016-08-17 17:11:56 -0600
> message:
>   Do not access-log chunked non-persistent responses with _ABORTED suffix.

> revno: 14805
> branch nick: trunk
> timestamp: Wed 2016-08-17 16:46:38 -0600
> message:
>   Do not access-log SslBump-faked CONNECTs with _ABORTED suffixes.


Our second fix might be related to your problems.

Alex.



More information about the squid-users mailing list