hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: Three different HttpContext in HttpAsyncService
Date Tue, 07 Oct 2014 07:43:35 GMT
On Mon, 2014-10-06 at 19:42 +0400, Dmitry Potapov wrote:
> On Mon, Oct 06, 2014 at 03:49:42PM +0200, Oleg Kalnichevski wrote:
> > Could you please put together a test case demonstrating such execution
> > path?
> Here it is: https://gist.github.com/hirthwork/45a45702a112c14b041d
> I've modified NHttpFileServer example a bit, so it will throw ProtocolException
> if file not found.
> At the start of execution I'm putting timestamp into context using
> HttpRequestInterceptor and in ConnectionKeepAlive strategy tries to get request
> and timestamp from context.
> Everything works fine if there was no exception (context is the same as one
> passed to http processor).
> In case of exception original context is lost, so it will contain only response
> object.

I see the problem now. If we want to support propagation of the current
context to the HttpAsyncService#exception method I do not see a way
around storing it in the State object.

Would you like to put together a patch?


To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org

View raw message