<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>(related to Akamai message from before-- but I have better troubleshooting information).<br><br>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).<br><br>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".<br><br>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.<br><br>I've tried adding "delay = yes" and "sni = test.authorize.net", but neither work.<br><br>To see this in action, a simple setup with any accept, then connect to test.authorize.net:443 in client = yes mode.<br><br>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<br><br>This is what you'll get if you try to use stunnel (400 invalid url) : <a href="https://23.195.204.150/gateway/transact.dll" target="_blank">https://23.195.204.150/gateway/transact.dll</a><br><br>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?<br> </div></body>
</html>