Re: [squid-users] cannot leave empty workers

2015-07-25 Thread Alex Wu
create it, and wokrer just attaches to it. Alex > Subject: Re: [squid-users] cannot leave empty workers > To: alex_wu2...@hotmail.com; squid-users@lists.squid-cache.org > From: squ...@treenet.co.nz > Date: Sat, 25 Jul 2015 12:54:47 +1200 > > On 25/07/2015 11:53 a.m., Alex Wu

Re: [squid-users] cannot leave empty workers

2015-07-24 Thread Alex Wu
cannot leave empty workers > > On 25/07/2015 7:24 a.m., Alex Wu wrote: > > If I define 4 workers, and use the following way to allocate workers: > > > > if ${process_number} = 4 > > //do something > > else > > endif > > The "else" means th

Re: [squid-users] cannot leave empty workers

2015-07-24 Thread Alex Wu
. THX Alex > To: squid-users@lists.squid-cache.org > From: squ...@treenet.co.nz > Date: Sat, 25 Jul 2015 10:07:18 +1200 > Subject: Re: [squid-users] cannot leave empty workers > > On 25/07/2015 7:24 a.m., Alex Wu wrote: > > If I define 4 workers, and use the following

[squid-users] cannot leave empty workers

2015-07-24 Thread Alex Wu
If I define 4 workers, and use the following way to allocate workers: if ${process_number} = 4 //do something else endif I leave other workers as empty after else, then we encounter this error: FATAL: Ipc::Mem::Segment::open failed to shm_open(/squid-ssl_session_cache.shm): (2) No such file or

Re: [squid-users] SSL connction failed due to SNI after content redirection

2015-07-22 Thread Alex Wu
we can intercept HTTP requests at squid, Alex > To: squid-users@lists.squid-cache.org > From: squ...@treenet.co.nz > Date: Thu, 23 Jul 2015 00:21:31 +1200 > Subject: Re: [squid-users] SSL connction failed due to SNI after content > redirection > > On 22/07/2015 12:44 p.m.,

Re: [squid-users] SSL connction failed due to SNI after content redirection

2015-07-21 Thread Alex Wu
it depends on how you set up squid, and where the connection is broken. The patch addessed the issue that occured using sslbump and content redirect together. Alex > Date: Tue, 21 Jul 2015 17:27:43 -0700 > From: hack.b...@hotmail.com > To: squid-users@lists.squid-cache.org > Subject: Re: [squid

Re: [squid-users] SSL connction failed due to SNI after content redirection

2015-07-21 Thread Alex Wu
The patch has been manually modified to meet code review. Here is the patch without any manuall modification: diff --git a/squid-3.5.6/src/ssl/PeerConnector.cc b/squid-3.5.6/src/ssl/PeerConnector.cc index b4dfd8f..d307665 100644 --- a/squid-3.5.6/src/ssl/PeerConnector.cc +++ b/squid-3.5.6/src

Re: [squid-users] SSL connction failed due to SNI after content redirection

2015-07-20 Thread Alex Wu
Subject: Re: [squid-users] SSL connction failed due to SNI after content > redirection > > On 07/20/2015 11:28 AM, Alex Wu wrote: > > With 3.5.6 code, we found one thing is broken. > > > > We used pyredir to rewrite request to a surrogated server enabled SSL > > co

Re: [squid-users] SSL connction failed due to SNI after content redirection

2015-07-20 Thread Alex Wu
connction failed due to SNI after content > redirection > > On 07/20/2015 11:28 AM, Alex Wu wrote: > > With 3.5.6 code, we found one thing is broken. > > > > We used pyredir to rewrite request to a surrogated server enabled SSL > > connection. > > > > Als

[squid-users] SSL connction failed due to SNI after content redirection

2015-07-20 Thread Alex Wu
With 3.5.6 code, we found one thing is broken. We used pyredir to rewrite request to a surrogated server enabled SSL connection. Also, we enable this in squid.conf: url_rewrite_host_header on We expect a request to www.foo.com is changed to www.foo-internal.com. squid sends the request with

Re: [squid-users] sslbump and caching of generated cert

2015-07-10 Thread Alex Wu
rs which are not under the process ids. Alex > Date: Fri, 10 Jul 2015 15:44:49 +1200 > From: squ...@treenet.co.nz > To: alex_wu2...@hotmail.com; squid-users@lists.squid-cache.org > Subject: Re: [squid-users] sslbump and caching of generated cert > > On 10/07/2015 7:03 a.m., A

Re: [squid-users] sslbump and caching of generated cert

2015-07-10 Thread Alex Wu
[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

Re: [squid-users] sslbump and caching of generated cert

2015-07-09 Thread Alex Wu
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. > > > > */ > >

Re: [squid-users] sslbump and caching of generated cert

2015-06-30 Thread Alex Wu
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

[squid-users] sslbump and caching of generated cert

2015-06-29 Thread Alex Wu
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