Based on your post, I was actually dug a little bit deeper because there was
nowhere in my Perl I could find that returned 1.
After disabling most of the Perl, I was getting 499 errors which made sense,
the client was closing the connection. It looks like part of the issue is
that attached to the
Hello!
On Tue, Apr 16, 2013 at 12:04:32PM -0400, abstein2 wrote:
> Sorry for the delay. I do think part of the issue is tied to the load
> balancer since that connection is timing out (we set it very low for testing
> purposes), but the load balancer terminating the connection doesn't explain
> w
Sorry for the delay. I do think part of the issue is tied to the load
balancer since that connection is timing out (we set it very low for testing
purposes), but the load balancer terminating the connection doesn't explain
why nginx is returning a 001 status code, since the connection from the
ngin
Hello!
On Wed, Apr 10, 2013 at 04:57:33PM -0400, abstein2 wrote:
> I can't find documention anywhere on what it means when nginx shows 001 as
> the value of $status in the access_log.
>
> I currently use nginx as a reverse proxy and I get this error when uploading
> large files (2+ MB though my
I can't find documention anywhere on what it means when nginx shows 001 as
the value of $status in the access_log.
I currently use nginx as a reverse proxy and I get this error when uploading
large files (2+ MB though my client_max_body_size is 4 MB) .
Also worth noting, the follow values per my
