>> You might adjusting the VIO nbytes to convince the VIO that it's finished all of its writing.
That's a good approach, then you can hook send response headers and adjust the final response to the client. Brian On Tue, Oct 29, 2013 at 3:32 PM, Alan M. Carroll < a...@network-geographics.com> wrote: > How do you return the EOS event? You would need to do it in response to a > normal IO call, instead of return WRITE_READY or similar. If you've already > read all the input, you'd need to return it on the write side. > > You might adjusting the VIO nbytes to convince the VIO that it's finished > all of its writing. > > I'm fighting with the same issue inside ATS, terminating a connection / > tunnel cleanly without crashing. > > Tuesday, October 29, 2013, 7:40:43 AM, you wrote: > > > A note about the operation of the plugin. > > The decision to abort the connection typically happens after all input > has > > been read, but before writing all the output. > > The plugin withholds (in a buffer) a certain amount of tail output, until > > it can be sure that the connection will not have to be aborted - that > > decision is dependent on the entire input. > > If everything is OK, the remaining withheld data is written out, > otherwise > > the transaction should be aborted. > > >
