Re: hc-4.3.6: AllowAllVerifier not used

2014-12-18 Thread Oleg Kalnichevski
On Wed, 2014-12-17 at 19:28 +, Pete Keyes wrote: > Thank you Oleg - very interesting. The only information that I see in the > JavaDoc is: > When a particular component is not explicitly this class will use its > default > implementation. System properties will be taken into accoun

Re: hc-4.3.6: AllowAllVerifier not used

2014-12-17 Thread Pete Keyes
Thank you Oleg - very interesting. The only information that I see in the JavaDoc is: When a particular component is not explicitly this class will use its default implementation. System properties will be taken into account when configuring the default implementations when

Re: hc-4.3.6: AllowAllVerifier not used

2014-12-17 Thread Oleg Kalnichevski
On Tue, 2014-12-16 at 18:08 +, Pete Keyes wrote: > Below is a unit test that attempts to use the > "SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER" option. It never > works and the wire level debug indicates that HC is always using > "BrowserCompatHostnameVerifier" instead. Can som

hc-4.3.6: AllowAllVerifier not used

2014-12-16 Thread Pete Keyes
Below is a unit test that attempts to use the "SSLConnectionSocketFactory.ALLOW_ALL_HOSTNAME_VERIFIER" option. It never works and the wire level debug indicates that HC is always using "BrowserCompatHostnameVerifier" instead. Can someone explain why or where my code is incorrect? WIRE LEVEL