[BrowsermobProxy] 1.1.9 version of browsermob for wilma cause unexpected problems on SSL connections

[tkohegyi]

Seems the upgrades of browsermod-proxy for Wilma from 1.0.8 to 1.1.9 causes unexpected problems in SSL connections, like this:

02:20:37.304 [SeleniumProxyHandler$SslRelay2-1] INFO  n.l.b.p.http.BrowserMobHttpClient - javax.net.ssl.SSLException: Received fatal alert: unexpected_message when requesting https://blah
02:20:37.414 [SeleniumProxyHandler$SslRelay1-1] INFO  n.l.b.p.http.BrowserMobHttpClient - java.net.SocketException: Connection reset when requesting https://blah
02:20:38.002 [SeleniumProxyHandler$SslRelay2-0] INFO  n.l.b.p.http.BrowserMobHttpClient - javax.net.ssl.SSLException: Received fatal alert: unexpected_message when requesting https://blah
02:20:52.276 [SeleniumProxyHandler$SslRelay4-1] INFO  n.l.b.p.http.BrowserMobHttpClient - javax.net.ssl.SSLHandshakeException: Insecure renegotiation is not allowed when requesting https://blah
02:20:52.342 [SeleniumProxyHandler$SslRelay4-1] INFO  n.l.b.p.http.BrowserMobHttpClient - javax.net.ssl.SSLHandshakeException: Insecure renegotiation is not allowed when requesting https://blah
02:21:55.445 [SeleniumProxyHandler$SslRelay2-0] INFO  n.l.b.p.http.BrowserMobHttpClient - javax.net.ssl.SSLException: Received fatal alert: unexpected_message when requesting https://blah
02:22:02.305 [SeleniumProxyHandler$SslRelay1-1] INFO  n.l.b.p.http.BrowserMobHttpClient - java.net.SocketException: Connection reset when requesting https://blah

therefore Wilma rolled back to use previous (1.0.8) version (5528ba)

Need investigation what change exactly caused this problem.
(Maybe this happens only when request/response is in Json, that is wired)

[tkohegyi]

Seems the problem with browsermob-proxy for wilma 1.1.9 release is fixed in this release:

'com.epam.wilma:browsermob-proxy:2.0-beta-8-wilma-1.1.32' 

Since this new version is published in jcenter, we will use it in the next Wilma release.
Note, that the actual Wilma version still use the 1.0.8 version from browsermob-proxy for wilma, that is reliable and working fine.

Btw the problem was caused by 3rd party libs those were upgraded, but the upgrade actually influenced (killed) the SSL/2-way-SSL function of the proxy. Solution was to downgrade the 3rd party lib version again.

(+ some other enhancement included in this version, see other browsermob-proxy related tickets)