I confirm - I've seen this issue in cache.log too.
16.02.16 11:25, Amos Jeffries пишет:
On 16/02/2016 3:12 p.m., Jason Haar wrote:
On Tue, Feb 16, 2016 at 2:48 AM, Amos Jeffries wrote:
Thanks for the reminder. I dont recall seeing a bug report being made.
Though Jason has sent me a more detai
On 16/02/2016 3:12 p.m., Jason Haar wrote:
> On Tue, Feb 16, 2016 at 2:48 AM, Amos Jeffries wrote:
>
>> Thanks for the reminder. I dont recall seeing a bug report being made.
>> Though Jason has sent me a more detailed cache.log trace to work with.
>>
>
>
> Yeah - I actually got half-way through
On Tue, Feb 16, 2016 at 2:48 AM, Amos Jeffries wrote:
> Thanks for the reminder. I dont recall seeing a bug report being made.
> Though Jason has sent me a more detailed cache.log trace to work with.
>
Yeah - I actually got half-way through putting in a bug report twice - but
ditched it for thi
On 15/02/2016 4:20 p.m., Dan Charlesworth wrote:
> Did a bug end getting filed for this?
>
> I can probably provide some ALL,9 logs but I don’t understand the problem
> well enough to write up a decent report I don’t think.
>
Thanks for the reminder. I dont recall seeing a bug report being made
Did a bug end getting filed for this?
I can probably provide some ALL,9 logs but I don’t understand the problem well
enough to write up a decent report I don’t think.
> On 12 Jan 2016, at 12:40 PM, Jason Haar wrote:
>
> Hi there
>
> I am finding squid-3.5.13 is false positive-ing on ssl-bump
On 12/01/2016 2:40 p.m., Jason Haar wrote:
> Hi there
>
> I am finding squid-3.5.13 is false positive-ing on ssl-bump way too
> often. I'm just using "peek-and-splice" on intercepted port 443 to
> create better squid logfiles (ie I'm not actually bump-ing) but that
> enables enough of the code to
Hey Jason,
I think we can divide the issue into two:
- host forgery identification
- host forgery action
And you can also add intercepting compared to configured forward proxy.
If you can draw a picture of the clients and the proxy network layout we
can try somewhere.
What you are talking about
Hi there
I am finding squid-3.5.13 is false positive-ing on ssl-bump way too
often. I'm just using "peek-and-splice" on intercepted port 443 to
create better squid logfiles (ie I'm not actually bump-ing) but that
enables enough of the code to cause the Host forgery code to kick in -
but it doesn't
