DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=37129>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=37129 Summary: User-defined ProtocolSocketFactory for secure connection through proxy Product: HttpClient Version: 3.0 RC4 Platform: Other OS/Version: other Status: NEW Severity: enhancement Priority: P2 Component: Commons HttpClient AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] I use a custom socket implementation with HttpClient, and am having problems getting secure connections through a proxy working. HttpClient requires that my SecureProtocolSocketFactory be able to create a secure socket layered over an existing insecure socket, but does not specify how that insecure socket is created. Currently, for secure proxied connections, the insecure connection is always created using a DefaultProtocolSocketFactory (HttpConnection.java, line 702). I wish to be able to override this behaviour, so that I can create the insecure socket using my own custom implementation. The problem with the default behaviour is that my custom socket implementation is written in C++ using JNI, and the SSL implementation is handled at the native level. Hence, layering over an existing JDK socket will not work. My proposed solution is to add an HTTP connection parameter to specify the socket factory to use, perhaps http.connection.insecuresocketfactory of type Class. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
