Hi
On 20 January 2011 05:37, Leo wrote:
[...]
> OK, here's an example of one such FTP server. curl can't connect without
> disabling EPSV: it waits for over a minute then fails. Cyberduck connects
> without problems, and so does curl with EPSV disabled.
>
> I'm on Mac OS X 10.5.8 with libcurl 7.1
On 1/19/11 2:07:46 PM, Daniel Stenberg wrote:
Thanks and I apologize for top-posting - just didn't pay attention.
I've been using curl for over 5 years already, never had any problems,
that's why I never really needed this group. :) It's been easy enough to
use to never require any assistance
On Thu, Jan 20, 2011 at 01:47:57AM +0200, Amr Shahin wrote:
> so after using the framework, i think it would be cool to add a couple of
> stuff, mostly related to organizing/aggregating the tests,
>
> * maybe we should add the ability to run the unit tests without running the
> whole bunch o
On Tue, Jan 4, 2011 at 1:00 AM, Daniel Stenberg wrote:
> Hi
>
> Thanks to Amr Shahin's persistance and work on the unit test front, I've
> just now pushed the work I've done so far on a unit test architecture for
> libcurl.
>
> I've documented the basic concept in tests/unit/README, and following
Hello,
the attached file contains a patch that will add a couple of test cases
to Curl_llist_insert_next, hopefully it covers all the cases.
let me know what you think.
*Amr*
0001-adding-3-test-cases-to-Curl_llist_insert_next.patch
Description: Binary data
--
On Tue, 18 Jan 2011, Quinn Slack wrote:
Your 0002-runtests-check-for-find_gnutls_serv.patch added the -q flag to
gnutls-serv, which suppresses a lot of debug info on the HTML page that it
serves. I've removed the -q flag in this patch. Does it work for you now?
I forgot to mention that the te
On Tue, 18 Jan 2011, Quinn Slack wrote:
Thanks a lot for your work on this! I've now committed and pushed this.
Tomorrow is feature-freeze day for 7.21.4 so this is most likely the last
feature we get in for this time.
Random notes on the tls auth work:
- I fixed test cases 1014 and 1119 to
On Wed, 19 Jan 2011, Leo wrote:
Right now I have several FTP servers to which any FTP client connects
instantly.
After reading your mail I realized you're here talking about connecting the
data connection, and I assume you mean in a passive manner.
libcurl will only connect to them instant
> > Regarding test 560 (use of axTLS with the multi interface), it turns
> out
> > that axTLS does not support non-blocking read/write operations.
> According
> > to Cam (axTLS maintainer) this is by design to keep the binary
> footprint and
> > memory use to an absolute minimum. The easiest thing
On Tue, 18 Jan 2011, Daniel Stenberg wrote:
> I think we should start with treating "STAT" special as I don't think there
> are that many other commands like it. If "STAT" is used instead of LIST or
> NLST, then libcurl shouldn't do any data connection at all.
>
> You up to making a patch for this
Thanks, Daniel!
That clarifies what happens under the hood. And, obviously, curl
connects perfectly to majority of servers.
However, I still wonder what to do from the practical point of view...
Right now I have several FTP servers to which any FTP client connects
instantly.
libcurl will
Sorry I wasn't clear enough. Actually I tried setting CURLOPT_SSL_VERIFYHOST to
0L but the result is same. Let me look into example.c again and post my
finding. In meantime, if you have any other tips to share, please do.
Thanks
anv
--
On Wed, 19 Jan 2011, valli.natara...@emc.com wrote:
Please don't top-post!
curl_easy_setopt(curl, CURLOPT_SSL_VERIFYPEER, 0L);
As I was kind of implying, and as I perhaps better spell out, setting only
CURLOPT_SSL_VERIFYPEER usually is not enough. That option verifies the cert's
aut
Thanks for reply. Basically, I want the client program to trust the server
identity. So I set following option
if (curl_global_init(CURL_GLOBAL_ALL) != CURLE_OK)
throw Exception("curl_global_init() failed");
if ((curl = curl_easy_init()) == NULL)
{
14 matches
Mail list logo
