<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Em 19/12/2018 16:29, Patrick Chemla escreveu:<br>
<blockquote type="cite"
cite="mid:001a1d99-bc22-149b-753c-d55aa74ba46a@performance-managers.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; </style>
<p>- Having more than one IP on the server, create SSL
certificates from LetsEncrypt including each a list of some
domains and sub-domains</p>
<p>- Create a very bing certificate to have squid using it (not
the best choice because domains are of different content, far
one to the other)<br>
</p>
<p>- Having squid managing all certificates on a single IP. (The
best because some domains have very high encryption needs, and
LetsEncrypt is not their preference)<br>
</p>
<p><br>
</p>
<p>Like a bottle in the sea: Is that possible, multiple
certificates, with squid 4.4 on a single IP?</p>
<p><br>
</p>
</blockquote>
Based on what I had researched recently, Squid still doesn't handle
SNI in accel mode, so you could set different, non-wildcard
certificates to the websites. See: <a moz-do-not-send="true"
href="http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-4-0-x-SNI-Support-td4682018.html">http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-4-0-x-SNI-Support-td4682018.html</a><br>
But it would be nice if Amos could confirm if this information is
still true for 4.4.<br>
</body>
</html>