On 21/07/2016 7:43 p.m., FredB wrote:
> Thanks Amos for your answer
> Do you think I can use an alternate method to tag my users requests ?
> Modifiy/add Header seems a bad idea
>
If its just between proxies, using HTTP messages. Then header should be
usable. This only falls over when you have
Ok thanks, so I will thinking about an another way ...
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
On 07/21/2016 10:33 AM, Alex Rousskov wrote:
> On 07/21/2016 12:41 AM, FredB wrote:
>> when I try to put some new headers it works only with an HTTP website
>>
>> I can't do that ? What are the limitations ?
> If you are intercepting SSL traffic, then you can do nothing today and
> will be able t
On 07/21/2016 12:41 AM, FredB wrote:
> I wonder what headers can be see by squid with a SSL website ? Without
> SSLBump of course
You are asking the wrong question if your goal is to "mark in logs a
specific information from a user for all proxies (proxy chaining)".
> when I try to put some ne
Thanks Amos for your answer
Do you think I can use an alternate method to tag my users requests ?
Modifiy/add Header seems a bad idea
Regards
Fred
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squ
On 21/07/2016 6:41 p.m., FredB wrote:
> Hello,
>
> I wonder what headers can be see by squid with a SSL website ? Without
> SSLBump of course
> In my logs I'm seeing User-Agent, Proxy-Authorization and some others but
> when I try to put some new headers it works only with an HTTP website
>
> I
Hello,
I wonder what headers can be see by squid with a SSL website ? Without SSLBump
of course
In my logs I'm seeing User-Agent, Proxy-Authorization and some others but when
I try to put some new headers it works only with an HTTP website
I can't do that ? What are the limitations ?
My goal i
