× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On 4/17/18, 11:11 AM, Krill, Coy wrote:
If you use a properties file to configure your application then set
these two properties properties based on your version of java being
used (examples below). If you don't use a properties file then you
will need to figure out a good place in your code to set these two
properties or set them from the command line. The document your
referenced has what you needed other than it skipped over the least
used property but the one probably most relevant to your situation.

Java 7+
https.protocols=" TLSv1.2,TLSv1.1,TLSv1 "
jdk.tls.client.protocols=" TLSv1.2,TLSv1.1,TLSv1 "

That didn't seem to have any effect at all. But after futzing around with it for two hours yesterday, a solution finally occurred to me:

Our current version instantiates and connects the SSLSocket in one swell foop:
SSLSocket s = (SSLSocket)factory.createSocket(adr, port);

If instead, I instantiate it and connect it in separate steps, I can then do a setEnabledProtocols() on it (if we're running under Java 7) BEFORE we connect it.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.