Hi,
On Sun, Jul 16, 2017, at 00:45, Viaduct Lists wrote:
>
> My point was that you can start the service as root, or set the user to
> root in nginx.conf. It’s confusing. Two ways. If I’m deliberately
> starting the service as root, why would I need to set the config file to
> indicate so?
>
> On Jul 15, 2017, at 6:24 AM, nanaya wrote:
>
>> If I deliberately start up using root, why would I need a directive that
>> indicates that? This directive seems like a reminder after the fact.
>>
>
> root is usually needed to bind port 80 and 443 so usually people want to
> start it using
Hello Nginx users,
(I forgot to send this out the other day...)
Now available: Nginx 1.12.1 for Windows
https://kevinworthington.com/nginxwin1121
(32-bit and 64-bit versions)
These versions are to support legacy users who are already using Cygwin
based builds of Nginx. Officially supported native
On Sat, Jul 15, 2017, at 18:56, Viaduct Lists wrote:
>
> > On Jul 15, 2017, at 5:04 AM, nanaya wrote:
> >
> >
> > It works if you start it from user with root privilege. Otherwise you
> > can't switch user and thus the directive is ignored.
>
> If I deliberately start up using root, why woul
Use my simple map/waf example (nginx-simple-WAF.conf) and some cleaver
regex's.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,275500,275511#msg-275511
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> On Jul 15, 2017, at 5:04 AM, nanaya wrote:
>
>
> It works if you start it from user with root privilege. Otherwise you
> can't switch user and thus the directive is ignored.
If I deliberately start up using root, why would I need a directive that
indicates that? This directive seems like a
Yes but characters in args like = & and ? are allowed and its when they
insert more than one occurance of them nginx accepts them and they bypass
any caches that you have.
&argument=value | Cache : HIT
&&&arguement===value | Cache : MISS
And when they want to DoS you they will do something like
Hi,
On Sat, Jul 15, 2017, at 17:47, Viaduct Lists wrote:
> The latter. It makes little sense. If it’s ignored then there’s no
> sense in having it.
>
It works if you start it from user with root privilege. Otherwise you
can't switch user and thus the directive is ignored.
> Much like how th
I fixed this issue. I found that uWSGI is a far better choices than
FastCGI for serving my Django app with nginx. :)
Cheers,
E
Le 2017-07-14 à 08:32, Etienne Robillard a écrit :
How can one debug the upstream FastCGI response from nginx?
Le 2017-07-13 à 10:25, Etienne Robillard a écrit :
The latter. It makes little sense. If it’s ignored then there’s no sense in
having it.
Much like how the current `nginx -t` report makes little sense as well:
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: [emerg] open() "/var/run/nginx.pid" failed (13: Per
10 matches
Mail list logo
