(related to Akamai message from before-- but I have better troubleshooting information).
I'm tying to route traffic through stunnel to a "cloud" based-endpoint. That endpoint has a static server name-- test.authorize.net. (This is the dev sandbox for auth.net).
But if you do an nslookup on test.authorize.net, you'll get back a different servername and IP, because it's so wonderfully "cloud".
Stunnel apparently tries to connect to the nslookup value. The server rejects the request because it can't route it back to test.authorize.net.
I've tried adding "delay = yes" and "sni = test.authorize.net", but neither work.
To see this in action, a simple setup with any accept, then connect to test.authorize.net:443 in client = yes mode.
This is what a valid response looks like (13 -- give me the darn merchant ID in a POST): https://test.authorize.net/gateway/transact.dll
This is what you'll get if you try to use stunnel (400 invalid url) : https://23.195.204.150/gateway/transact.dll
So how can I get stunnel to send the proper Request Header (host: test.authorize.net), make sure it's using http/1.1, etc?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20160517/d99b9034/attachment.html>