On Wed, Feb 1, 2017 at 3:44 PM, Dave Page <dpage@pgadmin.org> wrote:
On Wed, Feb 1, 2017 at 10:11 AM, Harshal Dhumal <harshal.dhumal@enterprisedb.com> wrote: > Hi, > > When I setup my machine with below server setup and without proxy_redirect I > got slightly different behaviour. In my case all redirects were failing > cause browser was redirecting all request to http while server (nginx) was > configure to serve only https. I didn't get any intermittent state like > pgAdmin4 front page was loading but other requests (like css, js) was > failing. > > Issue was when pgAdmin4 app returns redirect (301 /302) response to apache > and apache to nginx; the nginx was returning redirect location header as is > (i.e. with http protocol as apache was configured to accept only http) > > To avoid this I need to rewrite location header at nginx (proxy_redirect) > before sending it to browser. > > proxy_set_header X-Real-IP $remote_addr; > proxy_set_header X-Forwarded-For $remote_addr; > proxy_set_header Host $host; > proxy_pass http://127.0.0.1:81; > proxy_redirect http:// https://; > > With above nginx configuration pgAdmin was loading properly. > > Server setup: > > Nginx listing at 443 (https only) and forwarding all requests to apache at > 127.0.0.1:81 > Apache listing at port 81 (http only) with pgAdmin4 wsgi