Welcome! Log In Create A New Profile

Advanced

couple questions regarding log phase handlers

Anonymous User
July 07, 2014 04:50PM
In the log phase, what is the best way to determine if the client had
prematurely closed or aborted the request connection? To check
r->connection->error and look for HTTP_BAD_REQUEST someplace? Or possibly
check one of the members of the connection read or write structs?

Also, is the log phase resumable? It looks like all the log phase handlers
are looped through in
ngx_http_log_request() called from ngx_http_free_request(). However,
return codes are not checked. Was hoping for a way to return NGX_AGAIN
from within the log phase so that it could be resumable rather than
blocking. Possible? If not possible from within log phase, is there
another phase or output filter location that takes place after content
phase or content handlers have completed that is non-blocking and resumable?

Thank you!
_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

couple questions regarding log phase handlers

Anonymous User 572 July 07, 2014 04:50PM

Re: couple questions regarding log phase handlers

Maxim Dounin 278 July 07, 2014 06:30PM

Re: couple questions regarding log phase handlers

Yichun Zhang (agentzh) 402 July 07, 2014 06:50PM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 162
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready