Re: HttpClient 4.5.2 and Server Name Indication

2016-03-02 Thread Sam Wilson
On 3/2/16 3:51 PM, Oleg Kalnichevski wrote: On Wed, 2016-03-02 at 15:48 -0500, Sam Wilson wrote: On 3/2/16 3:41 PM, Oleg Kalnichevski wrote: On Wed, 2016-03-02 at 12:37 -0500, Sam Wilson wrote: Is there anything else I need to do to enable SNI? No, there is not. Just make sure you are not

Re: HttpClient 4.5.2 and Server Name Indication

2016-03-02 Thread Oleg Kalnichevski
On Wed, 2016-03-02 at 15:48 -0500, Sam Wilson wrote: > On 3/2/16 3:41 PM, Oleg Kalnichevski wrote: > > On Wed, 2016-03-02 at 12:37 -0500, Sam Wilson wrote: > >> > >> Is there anything else I need to do to enable SNI? > >> > > > > No, there is not. Just make sure you are not using deprecated > >

Re: HttpClient 4.5.2 and Server Name Indication

2016-03-02 Thread Sam Wilson
On 3/2/16 3:41 PM, Oleg Kalnichevski wrote: On Wed, 2016-03-02 at 12:37 -0500, Sam Wilson wrote: Is there anything else I need to do to enable SNI? No, there is not. Just make sure you are not using deprecated functionality. I'm sorry, are you saying that I am using deprecated

Re: HttpClient 4.5.2 and Server Name Indication

2016-03-02 Thread Philippe Mouawad
Hi, Have a look at this: https://issues.apache.org/jira/browse/HTTPCLIENT-1119 You will see concerned classes, see: https://github.com/apache/httpclient/commit/92b7e8cd971868505d0f22ee5cfc12a68ee91b80#diff-4f1f0cfa92ca97f7ee68436780ce874c See Oleg's commit few minutes on deprecated classes:

Re: HttpClient 4.5.2 and Server Name Indication

2016-03-02 Thread Sam Wilson
On 3/2/16 3:56 PM, Philippe Mouawad wrote: See Oleg's commit few minutes on deprecated classes: http://svn.apache.org/viewvc?view=revision=1733362 So yes, my code hits that change. I take it I either grab the latest HttpClient from svn, or change my software to avoid this path? Thanks for

Re: HttpClient 4.5.2 and Server Name Indication

2016-03-02 Thread Oleg Kalnichevski
On Wed, 2016-03-02 at 12:37 -0500, Sam Wilson wrote: > Hey httpclient-users, > > I'm trying to get Server Name Indication working in an existing > application, but I'm having some serious trouble. > > The java version is 1.8.0_45. > > I've walked all the way through the HttpClient code to the

classloader issues in httpclient from jets3t in different classloader

2016-03-02 Thread Charles Allen
I'm getting the following stack trace when using jets3t which uses httpclient: Caused by: java.lang.IllegalStateException: Invalid class name: org.jets3t.service.utils.RestUtils$ConnManagerFactory at

Re: classloader issues in httpclient from jets3t in different classloader

2016-03-02 Thread Gary Gregory
Closing the loop: This should be fixed in trunk now. See https://issues.apache.org/jira/browse/HTTPCLIENT-1727 Gary On Wed, Mar 2, 2016 at 2:22 PM, Charles Allen wrote: > I'm getting the following stack trace when using jets3t which uses > httpclient: > > Caused

Re: classloader issues in httpclient from jets3t in different classloader

2016-03-02 Thread Alexey Panchenko
That was fast. I am just curious why making changes here :-) if - those classes were deprecated long ago? (the "java-deprecated" folder kind of reminds of that) - the code on jets3t master looks better and use newer httpclient APIs (its probably not released yet) On Thu, Mar 3, 2016 at 12:31 PM,