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 > why nginx is returning a 001 status code, since the connection from the > nginx box to the origin box shouldn't be affected by that. [...] > 2013/04/16 15:38:37 [debug] 28029#0: *629969 access phase: 9 > 2013/04/16 15:38:37 [debug] 28029#0: *629969 access phase: 10 > 2013/04/16 15:38:37 [debug] 28029#0: *629969 post access phase: 11 > 2013/04/16 15:38:37 [debug] 28029#0: *629969 try files phase: 12 > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl handler > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: "a" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: "v" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: "i" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: "r" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: "b" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: > "upstream_http_content_type" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl variable: > "upstream_status" > 2013/04/16 15:38:37 [debug] 28029#0: *629969 call_sv: 1 > 2013/04/16 15:38:37 [debug] 28029#0: *629969 perl handler done: 1 > 2013/04/16 15:38:37 [debug] 28029#0: *629969 http finalize request: 1, > "/panel/?" a:1, c:2 As per debug log, the request in question was finalized from a perl handler with status code 1. Likely just a bug in your perl code and it's meant to return 200. -- Maxim Dounin http://nginx.org/en/donation.html _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
