Forum OpenACS Q&A: Re: how to config for multiple aolserver instances

Collapse
Posted by Bart Teeuwisse on
Finally worked it out. The missing piece is indeed the CA cert. In AOLserver, one specifies the server cert, the server key and the CA cert. Squid on the other hand only accepts the server cert and the server key.

What I couldn't figure out is where Squid gets the CA cert from. After several hours of reading code and googling I finally traced the location of the CA certs. Squid relies on the CA certs provided with openssl. This explains why it worked for Brad but not for me. Our CA cert was not included in the default openssl list of CA certs.

The openssl CA certs are listed in /usr/share/ssl/cert.pem. Adding our CA cert to this list resolved the issue.

/Bart

Collapse
Posted by Bart Teeuwisse on

It appears that redirecting HTTP to HTTPS in Squid 2.5 is not trivial. From the squid-users archives:

Squid-2.5 has the peculiar limitation that requests accepted by https_port will internally be processed as http:// requests, meaning that http:// is sent to redirectors etc.

What you can do to differentiate http_port from https_port in squid-2.5 is to enable httpd_accel_port virtual, then look for the port number in your redirector, clean up the url etc.

Another option is to look into Squid-3.0 where this is a whole lot easier and does not require a redirector helper.

/Bart