[squid-users] Local port number logging woes

[Carl-Daniel Hailfinger]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Amos,

thanks a lot for your answer.

On 22.01.2015 05:22, Amos Jeffries wrote:
> On 22/01/2015 7:00 a.m., Carl-Daniel Hailfinger wrote:
> > I'm using cascaded/hierarchical Squid instances, one per machine.
> > [...]
>
> > This works great except for one oddity: Quite a few Squid log
> > entries of the child proxy have "0" as local port number of the
> > last server or peer connection. I have absolutely no idea why that
> > would be the case. AFAICS cached entries have "-" as local port
> > number and that's fine because it means there was no associated
> > parent proxy connection.
>
> > Am I doing something wrong? Are there any cases where the log
> > format code %<lp would legitimately yield 0?
>
> It is possible for connections which were never completely setup. The
> server/peer details will all be known, but the local TCP details will
> not be set by completion of the TCP handshake.

Ah, that may explain it. So this would only happen if the TCP connection
to the parent proxy can't be established completely.
A colleague of mine thought it might be related to parent proxy
connection keepalive. I'll forward your answer.

Thanks again!

Regards,
Carl-Daniel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iD8DBQFUwS1oRdNMz2eF/AERAv8kAJsF0XuTwBJvcy74MRpFrdJ7P5klQwCgnrg6
LEP4EkBarBc9qByymqo1hD0=
=fgvz
-----END PGP SIGNATURE-----