Welcome! Log In Create A New Profile

Advanced

Re: Status Code 001 In Logs

April 16, 2013 03:39PM
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 location I have a post_action that runs another perl method.

This Perl method doesn't have a return value and, in it's place, nginx is just using 001. When adding a return code to this method, it takes over the $status variable in the nginx log file. In general, have the method return $r->variable('status') seems to properly emulate exactly what codes the proxy is actual returning to the browser.

The one exception to this (that I can find) though is if the nginx return code was 499. Then I just see 009 in my log files. Is there anything better in nginx I can use than $status for getting the status code returned to the browser? Alternatively, is there anything I can do so that the log file doesn't read the status code from the post_action and instead just reads it from the initial location?
SubjectAuthorPosted

Status Code 001 In Logs

abstein2April 10, 2013 04:57PM

Re: Status Code 001 In Logs

Maxim DouninApril 11, 2013 08:28AM

Re: Status Code 001 In Logs

abstein2April 16, 2013 12:04PM

Re: Status Code 001 In Logs

Maxim DouninApril 16, 2013 12:24PM

Re: Status Code 001 In Logs

abstein2April 16, 2013 03:39PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 130
Record Number of Users: 7 on March 06, 2014
Record Number of Guests: 165 on April 21, 2014
Powered by nginx    Powered by FreeBSD    PHP Powered    Powered by Percona     ipv6 ready