I'll have to agree, I am lost in how to configure this and then determine that it is truly speaking ssl. I'm adding cache_peer configuration(s) and not seeing anything break or change. I want to see in the end result that SSL is the only option and no other communication is allowed. I have setup the servers where SQUID2 accellerates the webserver then SQUID1 accellerates SQUID2. Maybe I should'nt be doing a "double accelleration" where I am using SSL to between the client and two SQUID servers only and not the webserver. I dunno.
Anyways I will compile Squid-3 and start working with it, but I am curious if you (Henrik, or any of the listers) have any sample configuration files or could give me cache_peer directive examples to where I have something to mold. client <---SSL-->SQUID1<---SSL--->SQUID2<---HTTP-->webserver ----- Original Message ----- From: "Henrik Nordstrom" <[EMAIL PROTECTED]> To: "mlister" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, March 25, 2003 12:09 PM Subject: Re: [squid-users] ssl between squid accellerators > tis 2003-03-25 klockan 16.09 skrev mlister: > > I have been poking around in the FAQ's and whitepapers trying to find how I > > can > > configure one squid accel. server to speak SSL to another. I have the SSL > > patch > > installed and both accellerators are configured as SSL servers using > > identical certs. > > I am not sure if I should be trying to configure some kind of peer or what. > > cache_peer look like its in the general direction but looks more for a > > proxy. > > See the cache_peer directive in your patched Squid, or have a redirector > rewrite the requested URLs to https:// > > This kind of thing will be a lot easier in Squid-3 with it's new > accelerator support. > > Regards > Henrik > > -- > Henrik Nordstrom <[EMAIL PROTECTED]> > MARA Systems AB, Sweden >
