On Fri, Jul 14, 2017 at 10:40:27AM -0400, Viaduct Lists wrote:
> > On Jul 14, 2017, at 9:29 AM, Francis Daly wrote:
Hi there,
> > In unix land, usually, if a process starts running as root, then it is
> > able to "switch" to run as another user. If a process starts running as
> > non-root, it is
I took the opposite approach. You put a funny character in the URL, you get a
444. I only allow underscore and hypen.
For a while, I was getting fuzzed. Maybe a year ago it was a thing. Nothing
bad happened, which I would say is a tribute to Nginx. I just returned 404s,
but I figured I better
But in actual use, you would just run nginx as a service, so I don't get the
sudo initiation. In fact, unless you run a very simple website, nginx alone
isn't sufficient, so you would be starting a number of services.
I make enough work for myself, but if security is an issue, I'd suggest setti
So I have been using Lua to iron out a few dilemmas and problems lately.
Does anyone know what characters Nginx accepts inside URL's
I am achieving a higher cache HIT ratio by modifying the URL's with Lua but
it also helps in preventing unwanted forms of DoS.
Here is my code :
local function fi
Hello,
>
> The error indicate that your backend server closed the connection.
> That's more less all nginx knows, so if you want to find out why
> your backend did this - consider looking into the backend.
>
i found the problem, there is by default a 180s timeout on my backend.
> Could you
OK, good to know. Thank you. This does suggest that security isn’t really
respected in this case.
Cheers
> On Jul 14, 2017, at 11:04 AM, Alberto Castillo wrote:
>
> I've just set up mine on a FreeBSD box and using sudo solves the
> problem, same issue with .pid.
_
Rich in T
On 07/14, li...@lazygranch.com wrote:
> I guess I'm missing something here since nginx should be invoke by "service"
> such as "service nginx restart".
>
> Original Message
> From: Alberto Castillo
> Sent: Friday, July 14, 2017 8:05 AM
> To: nginx@nginx.org
> Reply To: nginx@nginx.org
> Subje
I guess I'm missing something here since nginx should be invoke by "service"
such as "service nginx restart".
Original Message
From: Alberto Castillo
Sent: Friday, July 14, 2017 8:05 AM
To: nginx@nginx.org
Reply To: nginx@nginx.org
Subject: Re: FreeBSD Clean Install nginx.pid Permissions Erro
On 07/14, Jim Ohlstein wrote:
> Hello,
>
> On 07/14/2017 10:39 AM, Viaduct Lists wrote:
> >
> >> On Jul 13, 2017, at 9:31 PM, li...@lazygranch.com wrote:
> >>
> >> However the nginx process is owned by www:
> >> 823 www 1 200 28552K 7060K kqread 0:01 0.00% nginx
> >
> > Sure
Hello,
On 07/14/2017 10:39 AM, Viaduct Lists wrote:
>
>> On Jul 13, 2017, at 9:31 PM, li...@lazygranch.com wrote:
>>
>> However the nginx process is owned by www:
>> 823 www 1 200 28552K 7060K kqread 0:01 0.00% nginx
>
> Sure the process is owned, and is called upon by nginx
Hi there.
> On Jul 14, 2017, at 9:29 AM, Francis Daly wrote:
>
> In unix land, usually, if a process starts running as root, then it is
> able to "switch" to run as another user. If a process starts running as
> non-root, it is not able to switch to run as another user.
>
> And (usually) only r
> On Jul 13, 2017, at 9:31 PM, li...@lazygranch.com wrote:
>
> However the nginx process is owned by www:
> 823 www 1 200 28552K 7060K kqread 0:01 0.00% nginx
Sure the process is owned, and is called upon by nginx as the www user. The
`nginx -t` report is being called by ri
On Thu, Jul 13, 2017 at 06:58:02PM -0400, Viaduct Lists wrote:
Hi there,
> But sudo nginx -t gets rid of the error on nginx.pid
>
> That whole user/group issue on the user directive in nginx.conf is confusing
> as it ignores any attempt at using user root;.
In unix land, usually, if a proces
How can one debug the upstream FastCGI response from nginx?
Le 2017-07-13 à 10:25, Etienne Robillard a écrit :
Hi,
I'm trying to setup a Django app with nginx using fastcgi. Here's my
config:
# configuration file /etc/nginx/nginx.conf:
user www-data;
worker_processes 4;
pid /run/nginx.pid;
14 matches
Mail list logo
