[squid-users] HTTPS issues with squidguard after upgrading from squid 2.7 to 3.5

[Amos Jeffries]

On 16/06/2016 7:54 p.m., reqman wrote:
> Hello Eliezer,
> 
> first let me thank you for providing a complete and detailed
> explanation, I think I understand now what gives here.
> 
> Minor note: Amos is correct in stating that url_rewrite_access
> basically controls what is thrown into the redirector.
> 
> Now, before I opened this discussion I also came to the conclusion
> that to get rid of these issues, I had to avoid throwing HTTPS through
> a rewrite with squidguard. Indeed, setting the following solved the
> issue...:
> 
> ========================
> url_rewrite_program /usr/local/bin/squidGuard url_rewrite_children 8
> startup=4 idle=4 concurrency=0
> url_rewrite_access deny CONNECT
> url_rewrite_access allow all
> ========================

Just a warning to anyone reading this.

url_rewrite_program and url_rewrite_children are meant to be on
different lines.

Otherwise Squid will not obey the child process requirements defined by
url_rewrite_children.


The correct version of the above config snippet is:

 url_rewrite_program /usr/local/bin/squidGuard
 url_rewrite_children 8 startup=4 idle=4 concurrency=0
 url_rewrite_access deny CONNECT
 url_rewrite_access allow all

Amos