On 21/02/2011 18:16, Amos Jeffries wrote:
On 21/02/11 16:33, Pieter De Wit wrote:
Hi Amos,
just had a go at this:
request_header_access X-Forwarded-For deny
header_replace X-Forwarded-For
and it's still passing XFF from another source thru - Nothing to urgent
since the Deb6 boxes are getting
On 21/02/11 16:33, Pieter De Wit wrote:
Hi Amos,
just had a go at this:
request_header_access X-Forwarded-For deny
header_replace X-Forwarded-For
and it's still passing XFF from another source thru - Nothing to urgent
since the Deb6 boxes are getting built :) But if you spot something ?
Just
Hi Amos,
just had a go at this:
request_header_access X-Forwarded-For deny
header_replace X-Forwarded-For
and it's still passing XFF from another source thru - Nothing to urgent
since the Deb6 boxes are getting built :) But if you spot something ?
Cheers,
Pieter
Hi Amos,
Thanks for the reply - I remember seeing the doc bug :)
I am building the Deb6 boxes as we speak (ext4+squid 3.1 is sounding very
nice)
Cheers,
Pieter
On Mon, 21 Feb 2011, Amos Jeffries wrote:
On Mon, 21 Feb 2011 12:16:46 +1300 (NZDT), Pieter De Wit wrote:
Hi Guys,
I run a reve
On Mon, 21 Feb 2011 12:16:46 +1300 (NZDT), Pieter De Wit wrote:
Hi Guys,
I run a reverse proxy for a client. They are using XFF for
restricting certain content to IP.
We have noted that the following doesn't "appear" to work as it
should:
header_replace X-Forwarded-For allow all
My understa
Hi Guys,
I run a reverse proxy for a client. They are using XFF for restricting
certain content to IP.
We have noted that the following doesn't "appear" to work as it should:
header_replace X-Forwarded-For allow all
My understanding is that this will cause squid to replace the XFF header
wi