On 11/07/2015 11:02 a.m., Alex Wu wrote:
> actually, the major problems are:
>
> Once workers > 1, squid looks for /var/run/squid. pidfile for workers=1 is
> done in squid.conf, but for workers > 1, this will be ignored.
PID stands for "Process ID". The pidfile contains the process ID of the
Squ
t now.
Alex
From: alex_wu2...@hotmail.com
To: squ...@treenet.co.nz; squid-users@lists.squid-cache.org
Date: Fri, 10 Jul 2015 14:21:09 -0700
Subject: Re: [squid-users] sslbump and caching of generated cert
figured it out. It needs all helpers under the process id. I have content
redirect helpe
[squid-users] sslbump and caching of generated cert
>
> On 10/07/2015 7:03 a.m., Alex Wu wrote:
> > It seems the option http_port cannot be put under each process ID. If using
> > workers, http_port cannot bind to ports specified from http_port.
> >
>
> ?? Works for m
On 10/07/2015 7:03 a.m., Alex Wu wrote:
> It seems the option http_port cannot be put under each process ID. If using
> workers, http_port cannot bind to ports specified from http_port.
>
?? Works for me and many others.
What I dont expect to work is the *same* port line in two specific
workers
Subject: Re: [squid-users] sslbump and caching of generated cert
>
> On 1/07/2015 5:08 a.m., Alex Wu wrote:
> > /*
> > You could assign two workers, each with a different http_port and
> > ssl_crtd helper using different cert databases.
> >
> > */
> >
On 1/07/2015 5:08 a.m., Alex Wu wrote:
> /*
> You could assign two workers, each with a different http_port and
> ssl_crtd helper using different cert databases.
>
> */
>
> How to do this? It sounds it might meet our need.
>
at the top of squid.conf place:
workers 2
if ${process_number} =
a
diffrent port,
may need to set up a different CA.
THX
Alex
> Date: Tue, 30 Jun 2015 16:51:51 +1200
> From: squ...@treenet.co.nz
> To: squid-users@lists.squid-cache.org
> Subject: Re: [squid-users] sslbump and caching of generated cert
>
> On 30/06/2015 5:35 a.m., Alex Wu
On 30/06/2015 5:35 a.m., Alex Wu wrote:
> So far as I know, hen sslbump is enabled for a port, for each dns
> name, squid save a cert generated according to dns name and signing
> key (from http_port configuration). So the next time, the generated
> cert can be fetched if the same dns host and conf
So far as I know, hen sslbump is enabled for a port, for each dns name, squid
save a cert generated according to dns name and signing key (from http_port
configuration). So the next time, the generated cert can be fetched if the same
dns host and configured signing key.
Now have a question on t
