Nginx headers to be set at the time of request processing
Hi all, I understand that proxy_set_header sets headers before proxying the request to the upstream server. Is there some way I can set the headers at the time of request processing itself not just before proxying to upstream servers? Thanks, Sushma Posted at Nginx Forum: https://forum.nginx.org/read.php?2,271147,271147#msg-271147 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: Start nginx worker process with same user as master process
Thanks a lot Francis. Apparently nginx was once started as root. So automatically the ownership of the temp folders got changed to nginx user. This explains the sudden permission change even though I had set it explictly. Thanks for your help. Cheers, Sushma Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269006,269745#msg-269745 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: Start nginx worker process with same user as master process
Thanks for the details. I have explicitly changed permissions for directories as required. But the problem I am facing here is nginx reload fails due to permission denied for proxy_temp folder. I had explicitly changed permissions for this folder so that it could be accesssed by user abc (user with which nginx is running). However, when buffering happens, I see that the folder permissions are changed to be owned by nginx user. Hence my reload fails due to permissions issues. Is there something I am missing here? Does nginx remember the user with which it was installed and is that why these folder permissions are changing? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269006,269711#msg-269711 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Re: Start nginx worker process with same user as master process
Hi Francis, Thanks for your update. When nginx is installed (checking with -V option), I see that the user specified is "nginx" user. However my master and worker process are run as a different user (non root user). In this case I see that many of the directories in nginx are owned by nginx user. (probably bcos it was installed as nginx?). Is there a way to mention that I need this new user. nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /usr/local/nginx/conf/nginx.conf:6 Wth this , it looks like I cant change the user directive in nginx.conf file since it does not have any effect. Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269006,269677#msg-269677 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Log the headers sent by nginx to upstream server
My client sends a request to nginx with a http header set. This header is overwritten by nginx before passing along the reqest to the downstream server. I want to log the header after modification by nginx. I understand that we can log the header sent by client using "$http_". Is there some embedded variable or some other way I can use which will log the header sent to the downstream server? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269300,269300#msg-269300 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
Start nginx worker process with same user as master process
I have setup nginx master process with a user , lets say user1. In the nginx.conf, user directive is mentioned with nginx. (user nginx;) I understand that worker processes will be spawned by user nginx when I start nginx. Is there a way to start worker processes also as user1 without changing anything in the nginx.conf file ? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,269006,269006#msg-269006 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
SNI support for nginx
Hi, I am relatively new to nginx. I would like to setup multiple domains on the same port. Nginx has SNI support enabled. Do i have to still point to the right ssl certificate and ssl private in each of server blocks using the ssl_certificate directive? Or is there a way, nginx will be able to dynamically figure out the cert to be presented without it being explicitly mentioned via the directive ssl_certificate? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,268024,268024#msg-268024 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
