On 01/12/23 21:34, Amos Jeffries wrote:
On 1/12/23 04:55, Mario Theodoridis wrote:
I do have one more problem at this point.
Using openssl i can work with what i have below, but i cannot add a
2nd certificate
https_port 0.0.0.0:443 accel defaultsite=regify.com \
tls-cert=/etc/ssl/certs/
On 1/12/23 04:55, Mario Theodoridis wrote:
I do have one more problem at this point.
Using openssl i can work with what i have below, but i cannot add a 2nd
certificate
https_port 0.0.0.0:443 accel defaultsite=regify.com \
tls-cert=/etc/ssl/certs/regify.com.pem \
tls-cert=/etc/ssl/c
I do have one more problem at this point.
Using openssl i can work with what i have below, but i cannot add a 2nd
certificate
https_port 0.0.0.0:443 accel defaultsite=regify.com \
tls-cert=/etc/ssl/certs/regify.com.pem \
tls-cert=/etc/ssl/certs/foo.com.pem
gives me
ERROR: OpenSSL doe
Thank you Amos and Alex,
this is a config i managed to get working for http and https
acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 443 # https
# listeners
https_port 0.0.0.0:443 accel defaultsite=regify.com \
tls-cert=/etc/ssl/certs/regify.com.p
On 2023-11-28 05:29, Mario Theodoridis wrote:
Hello everyone,
i'm trying to use squid as a TLS virtual hosting proxy on a system with
a public IP in front of several internal systems running TLS web servers.
I would like to proxy the incoming connections to the appropriate
backend servers ba
On 28/11/23 23:29, Mario Theodoridis wrote:
Hello everyone,
i'm trying to use squid as a TLS virtual hosting proxy on a system with
a public IP in front of several internal systems running TLS web servers.
I would like to proxy the incoming connections to the appropriate
backend servers base
Hello everyone,
i'm trying to use squid as a TLS virtual hosting proxy on a system with
a public IP in front of several internal systems running TLS web servers.
I would like to proxy the incoming connections to the appropriate
backend servers based on the hostname using SNI.
I'm using the
