Re: Incorrect redirect protocol when behind a reverse proxy

te the > X-forwarded-proto header? > Thanks, I'll give these approaches a try. I don't know where else this might happen, though. Hopefully at some point I'll be able to say something like "override_protocol $http_x_forwarded_proto;" to tell nginx which protocol it&#

Re: Incorrect redirect protocol when behind a reverse proxy

root "data"; } } mkdir -p data/test/, and then accessing "http://localhost:1/test"; redirects to "http://localhost:1/test/";. -- Glenn Maynard ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Incorrect redirect protocol when behind a reverse proxy

cumentation wasn't helping. I was surprised to discover that the protocol seems to be hardcoded. > Do all requests have x-f-p? 100%? Then just change your redirects to > reference it. > I don't have any redirects. Nginx is doing this on its own. -- Glenn Maynard ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Incorrect redirect protocol when behind a reverse proxy

it doesn't look like there's any way to affect this in configuration. Is there any workaround? -- Glenn Maynard ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx