[stunnel-users] Requests to cloud server that requires host header

Wed May 18 05:19:31 CEST 2016

Lorne,
> 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?
Sorry. You can't. AFAIK stunnel have no support for user defined Headers. However, If you're not using a conventional web browser, you can modify the requests and insert any needed headers. You can do that with a library like libcurl.

regards,Jose

      From: Lorne Kates <halcyon1234 at hotmail.com>
 To: "stunnel-users at stunnel.org" <stunnel-users at stunnel.org> 
 Sent: Tuesday, May 17, 2016 3:03 PM
 Subject: [stunnel-users] Requests to cloud server that requires host header

(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?

_______________________________________________
stunnel-users mailing list
stunnel-users at stunnel.org
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stunnel.org/pipermail/stunnel-users/attachments/20160518/1d4d458f/attachment.html>