Forums Register Login

Forcing Commons HttpClient (3.1) to use TLS

+Pie Number of slices to send: Send
Hi,

A part of the web application (deployed on WebSphere - IBM-Java 1.4.2), creates HttpClient and calls the executeMethod(method). The target URL does not support SSL (v3/v2) anymore. Is there a way we can force the HttpClient to use TLS instead? I know that HttpClient 4.3.6 disables SSL (v3/v2) and supports TLS and 4.3.6 requires java 1.5. Is there a way out without migrating to HttpClient-4.3.6?

Thanks,
VenRa
I carry this gun in case a vending machine doesn't give me my fritos. This gun and this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com


reply
reply
This thread has been viewed 1808 times.
Similar Threads
Security
HTTPS over SSL/TLS
IBM Websphere 340
what is "locked because of migration" title in in hiernate site pages?
Replace METRO implementation for Web Services
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 29, 2024 03:35:02.