Sebb, I've had the chance to do a quick test today and the new property seems to work as expected!
When I set https.socket.protocols=SSLv3, all if working fine. If I set SSLv2 or SSL or any combination, it fails. I assume this is an issue with my application - I'll do some more tests end of the week and let you know. Thanks for your efforts! Steffen sebb schrieb: > OK, try again - new property as it does something different. > I kept the old property for now in case you need to play with both. > > https.socket.protocols=prot1 prot2 ... protn > > i.e. space separated list of protocols. > If you don't know what is supported, just use an invalid protocol and > it will log the supported ones. > > This is in nightly build r519694 just uploaded. > > S/// --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
