Hello,
I'm trying to configure a reverse proxy using Squid 2.6 to
serve pages from another server, using both http and https.
Lets say my cache server is mycache.net and I want to serve
both types of pages from cached.mycache.net. The result I'm
looking for is:
http://mycache.net/page -
On Tue, Oct 16, 2007 at 01:55:10PM +0300, Taneli Leppä wrote:
I'm trying to configure a reverse proxy using Squid 2.6 to
serve pages from another server, using both http and https.
I can get the configuration working so that http and https
go to destination site's http or https port, but not
Hello,
Michael Alger wrote:
My first question is, why do you want to do this?
We have our reasons. I agree it sounds strange.
My second question is, does squid actually do the SSL handshake
when you have it set up to connect to port 443 only? I've never
tried this so I have no idea if it
Amos Jeffries wrote:
I suggest adding defaultsite=mysite.example.net to those to help out
users with broken software.
Thanks for the suggestion!
add name=XX to the existing cache_peer
then add:
cache_peer cached.mycache.net parent 443 0 originserver name=YY
all cache_peer_access and
On tis, 2007-10-16 at 13:55 +0300, Taneli Leppä wrote:
Hello,
I'm trying to configure a reverse proxy using Squid 2.6 to
serve pages from another server, using both http and https.
http://mycache.net/page - http://cached.mycache.net/page
https://mycache.net/page -
Taneli Leppä wrote:
Amos Jeffries wrote:
I suggest adding defaultsite=mysite.example.net to those to help out
users with broken software.
Thanks for the suggestion!
add name=XX to the existing cache_peer
then add:
cache_peer cached.mycache.net parent 443 0 originserver name=YY
all
Amos Jeffries wrote:
Just one last: are people going to be visiting mycache.net? or
cached.mycache.net?
They're going to be visiting mycache.net, so I guess it's
correct.
cache_peer should use a private domain name or even IP address so you
can later change public DNS without breaking squid.
