tlb uses globally registered Protocol for schema="https", we should use a client specific HostConfiguration

lipinggm / tlb

Automatically exported from code.google.com/p/tlb

0 stars 0 forks source link

tlb uses globally registered Protocol for schema="https", we should use a client specific HostConfiguration #16

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

When using non absolute URIs this works.
This will avoid screwing up the environment for user's tests.

Original issue reported on code.google.com by singh.janmejay on 17 Dec 2010 at 7:57

GoogleCodeExporter commented 9 years ago

Original comment by itspa...@gmail.com on 17 Jan 2011 at 8:46

Added labels: Milestone-0.3

GoogleCodeExporter commented 9 years ago

Original comment by singh.janmejay on 26 Jan 2011 at 12:44

Changed state: Started

GoogleCodeExporter commented 9 years ago

done in: 8eeb864bcbdadce3269e5484a02961edd09d5992
moved to http-components as a part of this. Custom socket factory + trust 
manager deleted. RetryAction deleted. No retry is hooked up right now, we need 
to use http-components handler infrastructure. Retry logic on http-requests 
will be hooked up as a part of issue#49

Original comment by singh.janmejay on 28 Jan 2011 at 10:33

GoogleCodeExporter commented 9 years ago

Original comment by singh.janmejay on 28 Jan 2011 at 10:34

Changed state: Fixed