0

I have apache behind a NGINX reverse proxy that supports ssl. My backend apache server listens on HTTP only, so I use:

proxy_pass http://realip:8888;

however, this breaks the site because all URLs go to http, and chrome won't allow HTTP to load over HTTPS. How can I set the header as "https://" while sending over "http" to the backend apache server?

Improve this question

1 Answer 1

Reset to default
0

The best way to fix this is with the backend application. (Without knowing anything about the backend app, I'll try to give a general answer.)
Here are 2 options:

  1. Configure or modify the backend web application to use "https" when building links instead of detecting the protocol actually used.

  2. (better option) Configure or modify the backend web application to use the X-Forwarded-Proto header when building links. This header would be set in the nginx proxy like so: proxy_set_header X-Forwarded-Proto $scheme; Some installations, such as the Ubuntu packages, provide this in the proxy_params snippet and can be included like so: 'include proxy_params'.

Both of these options require the backend web app to support this specifically or you to be able to modify them to.

If the backend web application is building links based on the protocol used to contact it, like $_SERVER['SERVER_PROTOCOL'] for php, then there is no way to change that with the nginx proxy alone.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .