You are missing never_direct allow all
to force Squid to use your peer.. Note: Another option to use ssl between Squid and OWA is to use the front-end-https cache_peer option. This tells OWA that it should use https:// URLs even if the (inernal) connection was via HTTP. Regards Henrik ons 2003-01-29 klockan 15.13 skrev Adam Lewis: > I have a cache peer setup as follows... > > cache_peer pc1267.rtctel.com parent 443 442 ssl proxy-only > front-end-https=on ssl sslcert=/usr/local/squid/etc/owacert.pem > sslkey=/usr/local/squid/etc/owa.pem > > I also have > > httpd_accel_host pc1267.rtctel.com > > in the config. The name of the OWA server is pc1267.rtctel.com. I am real > close but when I goto https://pc1267.rtctel.com in my browser I authenticate > and then I'm back to http://pc1267.rtctel.com. It's as though it's SSL over > the authentication but when I'm authenticated it goes back to clear text. > Am I missing an option in the config? > > Thanks, > > Adam > > ----- Original Message ----- > From: "Henrik Nordstrom" <[EMAIL PROTECTED]> > To: "Adam Lewis" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, January 28, 2003 9:20 PM > Subject: Re: [squid-users] SSL error > > > > This error is/was seen if SSL failed to load the certificate. > > > > Regards > > Henrik > > > > > > Adam Lewis wrote: > > > > > > Hi, > > > > > > I'm receiving the following error when attempting to connect to > > > https://myserver. The error is from cache.log. I have compiled with > > > option --enable-ssl and patched squid for ssl with the SSL patch from > > > devel.squid-cache.org. Any ideas would be appreciated... > > > > > > __SNIP__ > > > > > > httpsAccept: Error allocating handle: error:140BA0C3:SSL > > > routines:SSL_new:null ssl ctx > > > > > > __SNIP__ > > > > > > Thanks, > > > > > > Adam > > -- Henrik Nordstrom <[EMAIL PROTECTED]> MARA Systems AB, Sweden
