[BUG] Posted requests not handled after dns resolving

lanshun zhou zls.sogou at gmail.com
Thu Mar 14 15:20:17 UTC 2013

Thanks~ And in the original patch, I introduced a variable c to save the
connection. I did
this because I think it may be not safe to continue using the variable r
after calling
ngx_http_upstream_finalize_request, in which the request struct and pool
may be freed.

2013/3/14 Maxim Dounin <mdounin at mdounin.ru>

> Hello!
> On Thu, Mar 14, 2013 at 06:44:48AM +0800, lanshun zhou wrote:
> > Because there is chance to call ngx_http_upstream_finalize_request in
> > function ngx_http_upstream_connect or it's sub calls, and i think this
> > makes no difference with failed resolution~
> Yes, you are right.  I'v committed slightly modified version of
> the patch.
> --
> Maxim Dounin
> http://nginx.org/en/donation.html
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20130314/1192079b/attachment.html>

More information about the nginx-devel mailing list