Search squid archive

Re: Re: Re: Re: Reverse proxy HTTPS to HTTP, with 2.6

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sam, nov 11 2006 - 00:23, Henrik Nordstrom wrote:
> fre 2006-11-10 klockan 15:19 +0100 skrev Joel CARNAT:
> 
> > Can I use the same squid "instance" (on port 80) to do the proxy and
> > reverse-proxy feature?
> 
> You can not use the same http_port for both purposes, but you can use
> the same instance with two different http_port.
> 

ah... here I have a problem... because I did it (with 2.5) and (finally)
achieved it with 2.6.

########################################################################
http_port 80 defaultsite=www.mydomain.net vhost
https_port 443 defaultsite=www.mydomain.net vhost cert=/etc/openssl/certs/www.mydomain.net.pem key=/etc/openssl/private/www.mydomain.net.key

cache_peer proxy.myisp.fr parent 3128 0 default
cache_peer www.mydomain.net parent 80 0 no-query originserver
cache_peer_domain proxy.myisp.fr !.mydomain.net
########################################################################


Now, I expect your answer to be "you can't do it the proper way".
Can you explain what is wrong in my conf dispite the fact that it works.

> But I recommend running two separate instances. Access control and
> request routing is a lot easier that way..

OK. In this case, can both instances share the same disk cache (and
memory cache) ?

TIA,
	Jo

[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux