On 23/12/2013 5:18 p.m., Nil Nik wrote:
Hello,
Please can u suggest where its going wrong?
Please explain didnt get client IP ?
* no X-Forwarded-For header added by the proxy?
* value unknown added by the proxy?
* an IP you did not expect was added by the proxy?
Amos
:03 -0500
Subject: Re: [squid-users] HTTP_X_FORWARDED_FOR for https request
yes that is true,
so with https sites using CONNECT this will not work,
but with an sslbump implementation in squid , which http headers can
you manipulate and then forward?
-Original Message-
From
Add this directive to your squid.conf file
forwarded_for on
The documentation for the directive is here:
http://www.squid-cache.org/Doc/config/forwarded_for/
-Original Message-
From: Nil Nik nil_fe...@hotmail.com
To: squid-users@squid-cache.org squid-users@squid-cache.org
Subject:
Unless you do SSL bumping, Squid will not touch the contents of HTTPS
connections.
--Will
On 11/22/2013 09:12 AM, Madhav V Diwan wrote:
Add this directive to your squid.conf file
forwarded_for on
The documentation for the directive is here:
: [squid-users] HTTP_X_FORWARDED_FOR for https request
Date: Fri, 22 Nov 2013 09:14:52 -0500
Unless you do SSL bumping, Squid will not touch the contents of HTTPS
connections.
--Will
On 11/22/2013 09:12 AM, Madhav V Diwan wrote:
Add this directive to your squid.conf file
forwarded_for
To: squid-users@squid-cache.org
Subject: Re: [squid-users] HTTP_X_FORWARDED_FOR for https request
Date: Fri, 22 Nov 2013 09:14:52 -0500
Unless you do SSL bumping, Squid will not touch the contents of HTTPS
connections.
--Will
On 11/22/2013 09:12 AM, Madhav V Diwan wrote:
Add