Curl 7.10.2 will not work with some https links. openssl version 0.9.6i-r2 Attempts to access some https links result in the following error message: curl: (52) Empty reply from server Attempts to access the same link from older versions of Curl/OpenSSL work fine. Attempts to manually ebuild 7.10.4 result in similar failures.
can you tell me which older version works?
On the old server, we had 7.9.8. As it turns out, it looks like it's the SSL version. The 7.9.8 curl running on the old server was compiled against OpenSSL 9.6b. When we downloaded OpenSSL 9.6i (which is what Gentoo has installed), the same error occurred.
ok thanks .. that makes more sense now from what i'm seeing. it looks like this happened with openhbci as well where it was incompatible with the newest openssl.
can you please try 7.10.5 in portage now? if it still doesn't work, can you give me a test case where it doesn't work? thanks.
www root # curl --version curl 7.10.5 (i686-pc-linux-gnu) libcurl/7.10.5 OpenSSL/0.9.6i zlib/1.1.4 www root # curl --url 'https://partners.networksolutions.com:8010/invoke/verisign.transactionproxy.Inbound/XMLAvailableProxy' curl: (52) Empty reply from server www root # Should look a little more like.... [root@naawww root]# curl --version curl 7.9.5 (i386-redhat-linux-gnu) libcurl 7.9.5 (OpenSSL 0.9.6b) (ipv6 enabled) [root@naawww root]# curl --url 'https://partners.networksolutions.com:8010/invoke/verisign.transactionproxy.Inbound/XMLAvailableProxy' <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE ErrorResponse SYSTEM "ErrorResponse.dtd"> <ErrorResponse> <ResponseHeader> <ReferenceNumber>001</ReferenceNumber> <Timestamp>2003-06-12T21:02:04EDT</Timestamp> </ResponseHeader> <Body> <StatusCode>-12000</StatusCode> <Description>XML is malformed</Description> <OriginalData> </OriginalData> </Body> </ErrorResponse> [root@naawww root]#
thanks. indeed that is weird. i'll try and contact the developer to see if he has any ideas about it. but according to this email, it seems like only the server knows: http://curl.haxx.se/mail/archive-2003-03/0039.html
http://sourceforge.net/tracker/index.php?func=detail&aid=745122&group_id=976&atid=100976 i've applied the patch to curl-7.10.5-r1 and it should work now. reopen if it still doesn't, but the test case works with the patched curl.
Much thanks. This is a much needed band-aid to hold things until we can switch to a native XMLRPC API. Shouldn't this be unmasked? -- Stuart P.S. Gentoo support is hands down some of the best I've ever seen thanks to people like you, Alastair
thanks for the encouragement. its been a couple of days and looks like it is safe to be in stable. especially since it fixes a long standing problem with 7.10.x with the new openssl.
