If really needed, there is a patch here
http://bugs.squid-cache.org/show_bug.cgi?id=3792
But as Amos said this patch is incomplete the CONNECT XFF header contents
should also be added to the bumped request
Fred
___
squid-users mailing list
squid-users@
>
> I have the same issue and racked my brain trying to find a solution.
> Now, I
> see there is no solution for this yet.
>
> I would appreciate so much if this feature were made available in the
> future.
>
> Eduardo Carneiro
>
>
Yes http://bugs.squid-cache.org/show_bug.cgi?id=4607
___
Amos Jeffries wrote
>>>
>>
>>
>> Ok thank you, there is a plan to add this ? Without identification we are
>> in the fog all bumped requests are only recorded with 127.0.0.1
>>
>
> Eventually, yes. I'm not aware of anyone actually working on it at
> present though.
>
> Amos
>
> __
On 15/09/2016 10:54 p.m., FredB wrote:
>
>>
>> Above are bumped requests sent inside the tunnel. Proxy #1 did not
>> interact with them, so it has no way to add XFF headers.
>>
>> The SSL-Bump logic does not yet store some things like indirect
>> client
>> IP and associate them with the bumped req
>
> Above are bumped requests sent inside the tunnel. Proxy #1 did not
> interact with them, so it has no way to add XFF headers.
>
> The SSL-Bump logic does not yet store some things like indirect
> client
> IP and associate them with the bumped requests.
>
> Amos
>
Ok thank you, there is a
On 15/09/2016 8:53 p.m., FredB wrote:
> Hello,
>
> I'm testing SSlBump and it works good, however I'm seeing something strange
> with two proxies and x-forwarded enabled to the first, some requests are
> wrote with the first proxy address.
>
> user -> squid (fowarded_for on) -> squid (follow_x
Hello,
I'm testing SSlBump and it works good, however I'm seeing something strange
with two proxies and x-forwarded enabled to the first, some requests are wrote
with the first proxy address.
user -> squid (fowarded_for on) -> squid (follow_x_forwarded_for allow all) ->
Net
Here log from th
