Solved Reverse or Forward Proxy Setup
-
So I have been working on a server that is running FreeBSD 7.3 which has been hosting a site for quite sometime. I was brought up to check and secure it as much as possible. I have setup the site with an Nginx Reverse proxy which is working properly.
Now the bigger problem is an authorize.net soap request that uses the Authorize.net API, this server has OpenSSL 0.98 which doesn’t support TLS 1.2 due to also the OS being out of support. What I have setup is a Forward proxy with Squid or Apache and both end with the same error of the Client being not supported even though is using the other Server as a proxy.
What I want to know is, am I right to think that regardless of what Forward proxy towards authorize.net the issue will be still the original client not supporting tls 1.2? Have any of you run into a similar situation and what do you recommend?
-
I was able to fix the issue with the following lines on Apache as Reverse Proxy
ProxyPass /soap/v1/ https://api.authorize.net/soap/v1/ ProxyPassReverse /soap/v1/ https://api.authorize.net/soap/v1/I assume this can also be done on Ngnix as well. So I will find out.
-
I am looking at this for right now
https://www.jeffgeerling.com/blog/2017/reverse-proxying-soap-api-accessed-phps-soapclient -
I was able to fix the issue with the following lines on Apache as Reverse Proxy
ProxyPass /soap/v1/ https://api.authorize.net/soap/v1/ ProxyPassReverse /soap/v1/ https://api.authorize.net/soap/v1/I assume this can also be done on Ngnix as well. So I will find out.
