On 29/03/2016 2:53 a.m., Marc Mapplebeck wrote:
> I am currently using squid for our proxy, and recently decided to use
> WPAD/PAC to also capture HTTPS traffic. I am having one very annoying
> issue with lightsquid, and wondering if anybody has any insight.
>
> All my lightsquid information look
On 03/28/2016 12:01 PM, Yuri Voinov wrote:
> 28.03.16 20:59, Alex Rousskov пишет:
>> On 03/27/2016 11:59 PM, Alexandr Yatskin wrote:
>>> Directive "deny_info" didn't work when we blocked https site with option
>>> "ssl_bump".
>> "deny_info" is not compatible with the ssl_bump "terminate" action.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
28.03.16 20:59, Alex Rousskov пишет:
> On 03/27/2016 11:59 PM, Alexandr Yatskin wrote:
>> Directive "deny_info" didn't work when we blocked https site with option
>> "ssl_bump".
>
> "deny_info" is not compatible with the ssl_bump "terminate" acti
On 03/27/2016 11:59 PM, Alexandr Yatskin wrote:
> Directive "deny_info" didn't work when we blocked https site with option
> "ssl_bump".
"deny_info" is not compatible with the ssl_bump "terminate" action. The
"terminate" action means "Close client and server connections". It is
impossible to serve
I am currently using squid for our proxy, and recently decided to use
WPAD/PAC to also capture HTTPS traffic. I am having one very annoying
issue with lightsquid, and wondering if anybody has any insight.
All my lightsquid information looks like the attached image. It also does
not consolidate t
I've already checked it. Order of this options doesn't matter.
28.03.2016 15:30, Yuri Voinov пишет:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I suggests the order is important and must be:
ssl_bump terminate blocked_https
deny_info http://www.example.com blocked_https
28.03.16 11:59,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I suggests the order is important and must be:
ssl_bump terminate blocked_https
deny_info http://www.example.com blocked_https
28.03.16 11:59, Alexandr Yatskin пишет:
> Directive "deny_info" didn't work when we blocked https site with option
> "
