That's great! Thanks a lot to both of you. On Wed, Oct 31, 2012 at 8:58 AM, Luca Colantonio <[email protected]> wrote:
> hi, > > if you'd like to see an example on how to do it you could have a look at > how the browsermob project does it in order to collect metrics: > > the custom ssl socket factory > > https://github.com/webmetrics/browsermob-proxy/blob/master/src/main/java/org/browsermob/proxy/http/TrustingSSLSocketFactory.java > > the custom ssl socket that sets the listener Oleg mentioned: > > https://github.com/webmetrics/browsermob-proxy/blob/master/src/main/java/org/browsermob/proxy/http/SimulatedSSLSocket.java#L26 > > hope that helps > > --luca > > On Wed, Oct 31, 2012 at 12:58 PM, Oleg Kalnichevski <[email protected] > >wrote: > > > On Tue, Oct 30, 2012 at 02:42:47PM -0700, John Sheehy wrote: > > > Hi all, > > > > > > using HttpComponents client 4.2.2, is there a way I can be notified > when > > an > > > SSL connection is ready for writing? I'm using a > > > PoolingClientConnectionManager and I think I need to somehow override > > > DefaultClientConnection's update() method which should be called when > the > > > TLS negotiation is complete, but I'm not sure how the plumbing works. > > > > > > Any help appreciated, > > > John. > > > > John > > > > JSSE API exposes a simple and effective mechanism of getting SSL protocol > > level notifications by registering a listener on an SSL socket instance > > > > > > > http://docs.oracle.com/javase/6/docs/api/javax/net/ssl/SSLSocket.html#addHandshakeCompletedListener%28javax.net.ssl.HandshakeCompletedListener%29 > > > > All it probably takes on the HttpClient side is a custom socket factory > or > > a hostname verifier. > > > > Oleg > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
