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 it was the application so I googled and found a some quick and dirty jsp pages that let me test the responses being passed back. For the apache server, I see the following:

Scheme: https
Name: my.example.com
Port: 443

Nginx responses show (regardless of how I try to connect):

Scheme: http
Name: my.example.com
Port: 80

I'm fairly new to nginx but I've read and googled fairly extensively to no avail.

I'm trying to do similar to the following:

location /myJWSapp/ {
proxy_pass http://127.0.0.1:8080;
proxy_redirect off;

proxy_set_header Host $http_host;
proxy_set_header X-Forwarded-By $server_addr:$server_port;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}

I can see the url in the jnlp file Also, for some reason the jnlp file is now being truncated at 10k (I've googled this to no avail as well). This is making it even more difficult to debug this issue.