I'm interested in running a Jetty server and having clients connect to it via HTTPS, and I'm trying to understand exactly how that would work in the WebFaction architecture.
Would the SSL handshake, decryption, and encryption all happen between the client and the front-end Nginx server and then communication between the Nginx server and Jetty would be in plain-text, so that the Jetty server would only need an HTTP listener and not also HTTPS?
Or would the encrypted message simply flow through the front-end Nginx server and Jetty would need to handle it with an HTTPS listener?
Thanks in advance for helping to clear this up.
asked May 23 '12 at 01:42
answered May 23 '12 at 02:09