Thank you Peter.
This would be a blocking point for Web Farms that rely on host headers.
On Wed, 6 Oct 2021 at 17:44, Peter Pentchev roam@ringlet.net wrote:
On Wed, Oct 06, 2021 at 05:04:24PM +0200, Alan C. Bonnici wrote:
Hi,
If I have the following in my stunnel [plivo-sni] client = yes accept = :23443 connect = api-ak.plivo.com:443 sni = *.plivo.com
And the following in my windows host file: 127.0.0.1 api-ak.plivo.com
Would that create a circular reference in STunnel?
Yes, that's why the log that you posted contains lines like:
2021.10.06 16:23:40 LOG6[0]: s_connect: connecting 127.0.0.1:443
...and then "connection refused", since your local machine does not have anything listening on port 443.
So... yeah. I'm not sure what would be the best way to handle this. If this were not Windows, I'd suggest running stunnel in a chroot environment that does *not* have api-ak.plivo.com in its hosts file, but unfortunately I have no idea how to achieve something like that under Windows.
G'luck, Peter
-- Peter Pentchev roam@ringlet.net roam@debian.org pp@storpool.com PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13