How to abort subrequest properly?

[Marat Dakota]

Hi Maxim,

Are there any adequately hardcore methods to close subrequest's connection?
I mean, what steps should be done internally?

For now, I'm just setting a flag in subrequest's context and just ignoring
the data in subrequest's body filter depending on this flag. It is ok, but
if there is a relatively simple way to close the connection to avoid
meaningless data transfers and meaningless waits for subrequest to be
finished — it would be nice.

Thanks.

--
Marat


On Wed, Jul 3, 2013 at 3:54 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:

> Hello!
>
> On Wed, Jul 03, 2013 at 04:34:26AM +0400, Marat Dakota wrote:
>
> > Nobody knows?
> >
> >
> > On Sun, Jun 30, 2013 at 3:04 PM, Marat Dakota <dakota at brokenpipe.ru>
> wrote:
> >
> > > Hi,
> > >
> > > I am parsing a subrequest's body as it arrives. At some point I could
> > > decide that the subrequest's body is not well-formed. I want to stop
> > > receiving the rest of the subrequest's body and close its connection.
> My
> > > main request and all other subrequests should continue working.
> > >
> > > I've tried something like ngx_http_finalize_request(sr, NGX_ABORT). It
> > > looks like it's not the thing.
> > >
> > > What steps should be applied to abort a subrequest?
>
> As of now, it's not really possible to abort a subrequest without
> aborting main request.
>
> --
> 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/20130703/8f4e283b/attachment.html>