I am currently in the process of setting up an internet facing IIS reverse proxy that will forward HTTP requests to an internal API server. I was able to get the server to work with the connection between the world and the reverse proxy over SSL, and the connection between the reverse proxy and API server running over plain HTTP. I attempted to set the API server to run on HTTPS with a self signed certificate, however I get a 502 Bad Gateway Error when attempted to access it through the proxy as before. I have a guess that the issue is with the self signed certificate because: The reverse proxy server is accessing the API via its Internal IP Address and not the name on the self signed certificate?
Also - Would I want SSL Offloading enabled or disabled? If it is disabled, would the proxy try to pass the certificate of the API to the client, or its own certificate? Would there be two separate SSL connections or one all the way through?
Any and all help is appreciated!