Hello Mr. Maxim, thank you very much for your reply. Things are much clearer now, thanks!
One, last question; I have implemented nginx as a reverse proxy with TLS termination in my FreeBSD host machine, and another nginx instance running in my jail, in; 10.10.10.2. So, the host machine does the reverse proxying and SSL. Before I open my website to public and production (a Wordpress website), could you please kindly have a look at my reverse proxy configuration here; http://paste.nginx.org/b8 So that you might wish to add some suggestions, or perhaps I still have a misconfigured/unneeded directive there? Thanks once again, Regards. Mark. Maxim Dounin <mdou...@mdounin.ru>, 19 Kas 2023 Paz, 03:05 tarihinde şunu yazdı: > Hello! > > On Sat, Nov 18, 2023 at 01:54:21PM +0300, Mark wrote: > > > Hello there. > > > > Having a proxy directive like; > > > > location / { > > proxy_pass http://10.10.10.4:4020; > > ... > > > > I wonder when using proxy_pass http://... (not httpS), > > are these directives effective, under the proxy_pass? > > > > proxy_ssl_name $host; > > proxy_ssl_server_name on; > > proxy_ssl_session_reuse off; > > > > Or they would work ONLY if proxy_pass is pointed to an "https://";? > > The "proxy_ssl_*" directives define configuration for SSL > proxying. That is, corresponding values are only used when > proxy_pass is used with the "https" scheme. > > -- > Maxim Dounin > http://mdounin.ru/ > _______________________________________________ > nginx mailing list > nginx@nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
