Thanks, Lucas. We looked at the headers being passed back (that's what the jsp was for). Even with http completely disabled and https only available, they were still passed as http:80 by nGinx...but Apache passed them through. We tried this on two separate environments. I looked at the ajp module. Unfortunately, it's not in any repository and custom builds are frowned upon for our systemby solitaryr - Nginx Mailing List - English
This apparently handles the proxying differently. Guess it's back to Apache since it handles it readily and has AJP support.by solitaryr - Nginx Mailing List - English
I'm sure this is probably just a misconfiguration or a misunderstanding of nginx proxying. I'm looking to replace apache as my ssl/proxy server for a Jboss/tcServer backend. Unfortunately, I have a java web start app that builds the jnlp files dynamically based on the scheme, protocol and server info passed back to it. I'm not getting the https (port 443) passed back as expected. I thought itby solitaryr - Nginx Mailing List - English