Ivan Artyukhin Wrote:
---
> configuration. I'm still confused why I can set this header for
> non-SSL port and I can't do it for SSL. What am I missing?
Maybe its a SNI thing, see also
http://forum.nginx.org/read.php?2,222512,222516#msg-222516
Backend correctly analyzes 'host' header. To check it I created simple
ServletFilter to 'set' this header and after it backend forms correct URLs.
So my problem will be solved if I manage to set 'host' header in nginx
configuration. I'm still confused why I can set this header for non-SSL port
and
With such backends you need to tell the backend that the origin is https,
otherwise it will 'think' its serving http since it is unaware of a proxy.
ea.
http://forum.nginx.org/read.php?2,254615,254618#msg-254618
___
nginx mailing list
nginx@ng
As soon as I uncomment '# proxy_set_header Host $host;' line it stops
working. All other headers don't matter
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,254615,254616#msg-254616
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.
I'm using Nginx as reverse proxy with SSL termination. The J2EE application
that is behind it sometimes uses host information to create URLs for popup
windows. Right now it inserts name of my upstream into URL and popup windows
are not launched (obviously). I understand that i have to fill 'Host' h
