You can try to use haproxy, nginx, varnish or any other proxy.

Eliezer

----
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: elie...@ngtech.co.il


-----Original Message-----
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf 
Of Amos Jeffries
Sent: Wednesday, April 12, 2017 7:13 PM
To: Maik Linnemann <maik.linnem...@provit.info>; 
squid-users@lists.squid-cache.org
Subject: Re: [squid-users] Squid 3.4.8 Reverse with multiple SSL Sites and 
multiple Certs/Domains

On 12/04/2017 7:58 p.m., Maik Linnemann wrote:
> Thanks Amos. Unfortunately i only have one public IP to use for the reverse 
> squid. I thought there might be an equivalent to apaches name based hosts or 
> similar. 

TLS protocol does contain SNI feature, but support for that in reverse-proxy is 
not yet complete.

You have a few other options that are less pleasing:

 * using a different port number instead of different IP, or

 * finding someone to complete the SNI reverse-proxy code in Squid, or

 * using a non-Squid proxy temporarily in front of Squid to split the traffic 
on SNI.

Amos

_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users

Reply via email to