Menu

#285 SSL to Roxen based hosts without explicit SSL version broken

closed-fixed
libcurl (356)
5
2013-06-21
2003-02-13
Anonymous
No

Hi. I am developing an app using CURLHandle framework for Mac OS X using Objective C. I have the latest CURLHandle code and my libcurl is 7.10.3 , running on Mac OS X 10.2.3.

The problem I have come across, is that a simple GET using https to certain hosts, fails with the below VERBOSE messages, if I do not explicitly set the SSL Version to 3. I have tried https GETs to various hosts, and many work fine, but my ISPs page and my own servers page (www.shire.net) give the below problem when I allow libcurl to determine which SSL to use and do not explicitly set it. I suspect the common element is the www server software in both cases of error is Roxen, with Apache and other servers seeming to work fine. Xmission is running Roxen 1.3 and I have Roxen 3.3... (www.roxen.com -- in Sweden).

I was not able to find in any publics docs what the 000000 error code might mean.

* About to connect() to www.xmission.com:443
* Connected to www.xmission.com (198.60.22.4) port 443
* SSL: error:00000000:lib(0):func(0):reason(0)
* Closing connection #0

Thanks
Chad
chad@objectwerks.com

Discussion

  • Daniel Stenberg

    Daniel Stenberg - 2003-02-13

    Logged In: YES
    user_id=1110

    The not-working without an explicit version number is a
    SSL-related thing, that I don't know how to fix. That is
    entirely left to OpenSSL to deal with. Feel free to audit
    how the OpenSSL API is used.

    The errror 0000 stuff is a bug in libcurl that makes it
    report wrong error number at times. If you get the recent
    source off CVS that particular error should be corrected.

     
  • Daniel Stenberg

    Daniel Stenberg - 2003-02-13
    • status: open --> open-fixed
     
  • Daniel Stenberg

    Daniel Stenberg - 2003-02-17

    Logged In: YES
    user_id=1110

    The 0000 thing is fixed, the other is a non-curl related SSL
    matter.

     
  • Daniel Stenberg

    Daniel Stenberg - 2003-02-17
    • status: open-fixed --> closed-fixed
     
MongoDB Logo MongoDB