Re: [squid-users] "unknown" in x-forwarded-for heder

From: Matus UHLAR - fantomas <uhlar@dont-contact.us>
Date: Fri, 1 Jun 2007 09:07:51 +0200

> Cc: squid-users@squid-cache.org, Matus UHLAR - fantomas <uhlar@fantomas.sk>
>
> > > I think it is all ok, but squid1, squid2, squid3 sometimes (for example
> > > when i use monitorurl in directive cache_peer) send "unknown" in
> > > x-forwarded-for header and therefor dansguardian is not able resolve
> > > correct ip and sends to squid4 in header 127.0.0.1. I just need to know
> > > why it sends unknown in this header.
> >
> > Well, for requests done to monitor the peer (monitorurl) there is no
> > client.

On 01.06.07 07:33, Juraj Sakala wrote:
> Yes, it is logical, but why squid puts unknown to header if no client. It
> should let it blank

Could you please stop ending private copies? I am subscribed to the list, I
don't need private reply.

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux IS user friendly, it's just selective who its friends are...
Received on Fri Jun 01 2007 - 01:07:58 MDT

This archive was generated by hypermail pre-2.1.9 : Sun Jul 01 2007 - 12:00:03 MDT