Hi sebb, I had feedback from one user facing the SNI issue and he confirmed issue is now fixed in nightly: - http://stackoverflow.com/questions/35430575/jmeter-aws-https-sni-issue
As it was agreed on in a previous mailing list discussion, HC3.1 is to be deprecated in 3.0 and removed in 3.1, so I think we have some time to fix it. Note there is also this one to be iso with HC3.1: - https://bz.apache.org/bugzilla/show_bug.cgi?id=57242 HC3 is deprecated for so many years now, I think removing it will encourage us to fix or report to HttpClient all remaining issues. We have I think fixed some remaining issues in next 3.0 and there is always the option to switch to java implementation. Regards On Wed, Feb 17, 2016 at 9:57 PM, sebb <[email protected]> wrote: > On 17 February 2016 at 12:50, Philippe Mouawad > <[email protected]> wrote: > > Hello, > > I think I have fixed the SNI issue with HTTPClient 4. Note it was strange > > that is worked with 3.1 and not 4.X. > > It would be great if you could test it and review fix. > > > > For me, this is a temporary fix until we upgrade the SSL Socket factory > in > > JMeter to use up to date classes from HttpClient 4.5.X > > > > This socket factory has at least 3 aims in my understanding: > > - Slow socket simulation > > - SSL Context reuse or not > > - Client SSL certificate management > > > > > > I think in 3.1 version we should at least drop all code related to 3.X > and > > Note that there was a recent email which suggested that HC3.1 worked > better than HC4.x for the recording function: > > > http://mail-archives.apache.org/mod_mbox/jmeter-user/201602.mbox/%3CCAOpZ4bk_U-0dx3JODwqbo3tiWgCWJwdx%2BWuH1v5NVHfOouvRxw%40mail.gmail.com%3E > > We should try and understand/fix that before dropping 3.1. > > > rework completely these part of the code as it is not easy to > > read/understand. > > > > -- > > Regards. > > Philippe > -- Cordialement. Philippe Mouawad.
