Hi Oleg, You know I am testing the asynchttpclient (and I know that you don't have lot of time to support this one). FYI the feedback is pretty good on HTTP, I've tested with a lot of concurrent requests. It seems stable as far as I have tested.
Now my problem is that I just put the SSLIOClientEventDispatch instead of the default HTTP one and when doing a small sequence of HTTP request, the first request is ok but the next one hangs...it never sends the second HTTP request. That seems strange as that should be transparent once the connection is ok (that has nothing to do with my previous mail on proxy as it has the same behavior with or without). Actually, it seems to miss the setting of WRITE event to the session after getting the HttpRequest. When debugging or pausing (or forcing the write everytime) it works. Could you please help as I'm really stuck at least to go more in tests with HTTPS on this one? BR, Fabrice -----Original Message----- From: Oleg Kalnichevski [mailto:[email protected]] Sent: mercredi 7 juillet 2010 14:40 To: HttpComponents Project Subject: RE: HttpCore NIO & SSL behind proxy On Wed, 2010-07-07 at 14:15 +0200, DELHOSTE Fabrice wrote: > Thanks, that helps a lot. > That is actually close to what I'm planning to do... > > However, do you think I can do all this by directly subclassing > SSLClientIOEventDispatch? > In other words, adding the CONNECT request to the newly created connection > first, overriding/wrapping SSLClientIOEventDispatch.createConnection (but how > do I get synchronously the result by submitting a request to that connection)? > And let the SSL dispatcher do the SSL job after? My personal recommendation would be to keep the i/o dispatcher protocol agnostic and move all protocol specific logic including HTTP CONNECT code to a custom protocol handler. Having said that, it should also be possible to achieve the same result by subclassing the SSLClientIOEventDispatch class. Cheers Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
