Just noticed that the failure above is very slightly different; it
prints "unexpected message" rather than "illegal parameter", although it
still goes away if you manually specify --sslv3.

I have servers which generate the "illegal parameter" error too, but
unfortunately they're not generally accessible from the internet. If
it's essential, though, I can probably make one available, or if not
then I'm happy to test patches locally.

-- 
Curl fails to open some https URLs with "illegal parameter" error
https://bugs.launchpad.net/bugs/595415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to