On Wednesday 30 May 2007 18:58, Matus UHLAR - fantomas wrote:
> > On Wednesday 30 May 2007 10:36, you wrote:
> > > Juraj Sakala escribió:
> > > > Hi,
> > > >
> > > > please can someone explain me why the value unknown is in
> > > > x-forwarded-for header?
> > >
> > > Do you have enabled the forwarded_for directive in squid.conf?
>
> On 30.05.07 14:25, Juraj Sakala wrote:
> > yes, i have
>
> enabled means it's set to 'on'. IS this correct on your server?
My infrastructure looks like this:
(squid1) ------|
|
(squid2) ------ (dansguardian, squid4) ------- INTERNET
|
(squid3) ------|
This is relevant part of my config on squid1, squid2, squid3, squid4 :
forwarded_for is on
follow_x_forwarded_for allow all
acl_uses_indirect_client on
log_uses_indirect_client on
This is relevant part of my config on dansguardian
forwardedfor = on
usexforwardedfor = on
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.
Thanks for help
Juraj
