On Sat, Aug 31, 2013 at 11:57 AM, Thomas Dineen wrote:
> For both Solaris 10 and Fedora 14
Fedora 14 hasn't been supported since 2011, and many of its libraries
are very old now.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827
-parse the XML is also a bundled libcurl
example [2].
[1] https://github.com/pantheon-systems/fusedav
[2] http://curl.haxx.se/libcurl/c/xmlstream.html
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List
n with
non-blocking sockets? If not, could there be a flag to force blocking
behavior to allow fail-over to occur?
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/lis
>From the project web page:
> In practice, only the OpenSSL and GnuTLS variants seem to see widespread
> deployment.
Except for *every installation of Fedora, RHEL, CentOS, and Scientific Linux*.
---
List admin: http://cool.haxx.se/l
I see some exciting pipeline-management features landing in new cURL
releases that balance connections to the same hostname. Is there any
interest in extending such support to balancing/fail-over between
multiple A/ records returned for a domain? Since cURL seems to
prefer its own DNS client, i
The share interface documentation [1] specifies that DNS lookups and
cookie data get shared, but is there an exhaustive list of what gets
shared? Specifically, do persistent connections get shared?
[1] http://curl.haxx.se/libcurl/c/libcurl-share.html
--
David Strauss
| da...@davidstrauss.net
I've sent in a patch to the docs.
On Wed, Apr 10, 2013 at 10:31 PM, Nick Zitzmann wrote:
>
> On Apr 10, 2013, at 6:32 PM, David Strauss wrote:
>
>> The share interface documentation [1] specifies that DNS lookups and
>> cookie data get shared, but is there an ex
What is the output of curl -V? The SSL/TLS library cURL is linked to
has a major impact on how it performs system-level validation.
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/eti
ace to remove access to any system-level trusted certificates.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl
On Thu, Apr 11, 2013 at 1:39 PM, Daniel Stenberg wrote:
> Apple has added some magic for certificate verification in their OpenSSL
> version.
Apple OS X has a certificate management system that might even be
accessible within a chroot.
-
simply returns the number of
bytes sent in, and (3) CURLOPT_PROGRESSFUNCTION (with
CURLOPT_NOPROGRESS set to zero) to cancel after the body starts. Part
#3 is optional.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [
On Thu, Apr 11, 2013 at 1:40 PM, David Strauss wrote:
> (3) CURLOPT_PROGRESSFUNCTION (with
> CURLOPT_NOPROGRESS set to zero) to cancel after the body starts.
Here's a good write-up on how to do that:
http://curl.haxx.se/mail/lib-2009-04/0296.html
--
David Strauss
| da...@david
Oh, actually it looks like you can make the transfer "fail" right from
the CURLOPT_WRITEFUNCTION, which means you could just have it return
zero. You would have to expect libcurl to consider the request failed,
though.
On Thu, Apr 11, 2013 at 1:46 PM, David Strauss wrote:
> On Thu,
y using weights.
If this were implemented, we would also use it for our PHP and Python
API clients, which also connect through load balancers but don't run
into as many saturation issues.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
--
On Sat, Apr 13, 2013 at 3:12 AM, Steve Holme wrote:
> Whilst I have 20 odd years' experience as a C/C++ developer would someone
> be so kind to check the four uses of sscanf() in url.c between lines 4381
> and 4402 to see if this is the best / most optimal way of extracting the
> user, password an
m sure it's also possible programmatically using the OpenSSL API.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: htt
lly easier to prove correctness of a full fledged lexer/parser or
> separate library? I can't see how that can be...
A quality lexer/parser guarantees that a specified grammar lacks
ambiguity and that crazy/malicious input patterns get handled safely.
--
David Strauss
| da...@davidstrau
s
stream parser:
https://github.com/pantheon-systems/fusedav/blob/curl/src/props.c
Is there interest in ls-style output for WebDAV, provided the path
ends in a slash and an option gets set?
--
David Strauss
| da...@davidstrauss.net
| +1 512 5
like
the header write callback, which provides the called function with a
more coherent unit of data rather than a buffer of incoming bytes.
>From a layering perspective, though, this could all live in a new
library that provides libcurl-compatible write callbacks for directory
listings that abstract
onsistent listing support to extend to
IMAP, DICT, and other cURL protocols, too.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
libssh2_strerror(err));
> state(conn, SSH_SFTP_CLOSE);
> sshc->nextstate = SSH_NO_STATE;
> -sshc->actualcode = CURLE_QUOTE_ERROR;
> +sshc->actualcode = sftp_libssh2_error_to_CURLE(err);
> break;
>}
>state(conn, SSH_SFTP_NEXT_QUOTE);
>
> They allow to get better error codes
o become
>>> sftp_libssh2_error_to_CURLE()
>>> is not really related to the new callback and I would ask you to submit
>>> that
>>> as a separate patch (which we could merge at once)
>>
>> I'm not entirely sure about this one. This would make it impossible to
>> tell
>> when an error was due to a quote command or when it was due to a
>> subse
Along the mailing list etiquette lines, sorry for my top-post. That's
not cool, either.
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
good home in the documentation for what the split in
responsibilities is between libcurl and a user of the library? Is
there interest in adding optional Content-MD5 support?
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [m
Does the counter for CURLOPT_LOW_SPEED_TIME start as soon as the
connection establishes, or does it wait until the response starts
coming back? I'm curious about the case of a server that takes, say,
60 seconds to prepare the response but sends it back in one burst.
--
David Strauss
implement this for our own server/client communication
and our communication with S3, so the set of implementations needing
to interoperate is pretty limited. The goal is to checksum, not to
avoid attacks. MD5 is quite adequate for that. I would like to use a
standard rather than rolling our own m
er.c:1029
#15 0x0033fe82937d in Transfer (conn=0x7fb8c386b600) at transfer.c:1396
#16 Curl_do_perform (data=0x7fb8c387c000) at transfer.c:2108
#17 0x0033fe82982b in Curl_perform
(data=data@entry=0x7fb8c387c000) at transfer.c:2232
#18 0x0033fe829d0c in curl_easy_perform
(curl=curl@entry=0x7fb8
On Wed, May 1, 2013 at 12:28 PM, David Strauss wrote:
> What timeouts should we be configuring to give up faster when
> it's in this state?
Based on empirical data, it looks like CURLOPT_TIMEOUT is taking
effect, but I'm curious is there's a more precise way to time out
he
S SRP?
> * You're missing a full stop at the end of the QSOSSL details line -
> "OS/400" should be "OS/400." for consistency ;-)
>
> I hope my feedback helps
>
> Steve
> ---
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http
MEOUT, 60 * 3);
Is this an NSS bug, or is it an issue with how libcurl uses NSS? I'm
on Fedora 17 with libcurl 7.24.0 and NSS 3.14.3.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
On Tue, May 7, 2013 at 1:46 PM, David Strauss wrote:
> NSS seems stuck in poll loop, which has been going on for hours
Actually, I'm not sure it's NSS stuck there. The loop could be higher
up. I just see an unending series of polls from strace.
--
David Strauss
| da...@dav
This -1 timeout is also in the current master:
https://github.com/bagder/curl/blob/master/lib/nss.c#L1518
On Tue, May 7, 2013 at 2:11 PM, David Strauss wrote:
> It looks like PR_Recv(conn->ssl[num].handle, buf, (int)buffersize, 0,
> -1) in nss_recv() (nss.c) may be the problem. That
It looks like PR_Recv(conn->ssl[num].handle, buf, (int)buffersize, 0,
-1) in nss_recv() (nss.c) may be the problem. That sets the timeout
for NSS to 4294967295.
On Tue, May 7, 2013 at 1:57 PM, David Strauss wrote:
> On Tue, May 7, 2013 at 1:46 PM, David Strauss wrote:
>> NSS seems s
://developer.mozilla.org/en-US/docs/PRIntervalTime
On Tue, May 7, 2013 at 2:14 PM, David Strauss wrote:
> This -1 timeout is also in the current master:
> https://github.com/bagder/curl/blob/master/lib/nss.c#L1518
>
> On Tue, May 7, 2013 at 2:11 PM, David Strauss wrote:
>> It looks like PR_Recv(con
late the remaining
timeout allowable for the request (considering how DNS, etc, have
already contributed to request time) and sending that in.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: h
On Tue, May 7, 2013 at 2:44 PM, Daniel Stenberg wrote:
> That's already done before the function is called in the first place. The
> the GnuTLS and OpenSSL versions of that function for example are completely
> non-blocking.
Well, then that sounds perfect!
--
David S
a backport of
the fix once it's in:
https://bugzilla.redhat.com/show_bug.cgi?id=960765
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-librar
On Tue, May 7, 2013 at 3:10 PM, Mel Smith wrote:
> I don't know *how* to revert to an earlier commit :((
git revert 8ec2cb5544
That will do a sort of reverse cherry-pick of that single change.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827
ay 7, 2013 at 2:59 PM, David Strauss wrote:
> On Tue, May 7, 2013 at 2:49 PM, Daniel Stenberg wrote:
>> Assuming it actually makes any difference for your case at least! ;-)
>
> If it means that it respects the timeouts we give, it's absolutely a
> fix for the problem we see
error immediately if the actual socket is non-blocking, polling it
returns EWOULDBLOCK, and the NSS non-blocking property is false.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=960765#c2
--
David Strauss
| da...@davidstrauss.net
| +1
On Wed, May 8, 2013 at 11:29 AM, David Strauss wrote:
> which I think it is now
I'm referring to very recent releases here, not "now" as in current
Fedora packages.
--
David Strauss
| da...@davidstrauss.net
| +1 51
On Wed, May 8, 2013 at 5:01 AM, Kamil Dudka wrote:
> Only the handshake still blocks with NSS.
Is there a way to fix this, too? Does it at least time out based on
the configured libcurl connection or request timeout?
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mob
On Wed, May 8, 2013 at 11:37 AM, David Strauss wrote:
> Does it at least time out based on the configured libcurl connection or
> request timeout?
Read some source and found the answer: yes.
timeout = PR_MillisecondsToInterval((PRUint32) time_left);
/* Force the handshake now *
made some
> trivial mistake, if this is the case please let me know, I would greatly
> appreciate it.
>
> source: http://pastie.org/pastes/7827550/text
> valgrind output: http://pastie.org/pastes/7827548/text
> curl version: 7.30.0
Your trace seems to be missing a lot
y here, I can say that the command-line curl uses libcurl. If
something is possible with the curl CLI, it's possible with libcurl.
There are a couple of cases where the curl CLI provides additional
logic, like HTTP retries, on top of libcurl. But, it's never redundant
with what libcurl
u want something like curl_easy_getinfo() with
CURLINFO_EFFECTIVE_URL [2]
[1] http://liboauth.sourceforge.net/
[2] http://curl.haxx.se/libcurl/c/curl_easy_getinfo.html
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [
On Tue, May 14, 2013 at 9:46 PM, Aldrich wrote:
> OK,I will try it.
That doesn't have any context as a reply to a digest.
Required reading: http://curl.haxx.se/mail/etiquette.html
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827
#x27;t require you to
fully manage the SSL context, but it is not portable to non-OpenSSL
backends for libcurl.
[1] http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#CURLOPTSSLCTXFUNCTION
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
--
On Thu, May 16, 2013 at 2:10 PM, Hu, Eric wrote:
> Regarding the patch itself, it still blocks in the connect phase.
This is true for the NSS SSL back-end, too.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mob
or any XML.
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
I've submitted an XML stream parsing example as a pull request:
https://github.com/bagder/curl/pull/66
I dropped the PROPFIND stuff for clarity. It's probably best to keep
it to basics for this first example.
---
List admin: http://co
I wanted to note that this is far more efficient than the existing
XML/HTML parsing examples. The existing examples pull the entire
response into memory before starting to parse. This new example only
allocates buffers to fit the character data between tags.
This is pretty important for our use ca
On Sun, May 19, 2013 at 2:22 AM, Daniel Stenberg wrote:
> ... and I've merged and pushed it already. Thanks!
Awesome! I verified that everything is clean using cppcheck, Clang
Analyzer, and Valgrind, so it should be solid.
--
David Strauss
| da...@davidstrauss.net
| +1 512
l/c/curl_easy_getinfo.html#CURLINFORESPONSECODE
--
David Strauss
| da...@davidstrauss.net
| +1 512 577 5827 [mobile]
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
transfer by returning 0 "pre-maturely" (i.e
before the server expected it, like when you've said you will upload N
bytes and you upload less than N bytes), you may experience that the
server "hangs" waiting for the rest of the data that won't come.
[1] http:
I know Daniel has his reservations, but I would love to see optional
Content-MD5 support in libcurl.
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
You could also just use an SSL sockets library directly or look at
ZeroMQ. libcurl isn't suited to using HTTP without the HTTP.
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquet
Yes, you should use your package manager (Yum). I'd like to note,
though, that Fedora 16 is not a supported release. Yum mirror
availability may be spotty.
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http
OS400 version >= 7.1).
> - QsoSSL is obsolescent.
>
> Your comments are welcome. If nobody objects, I'll commit it in a few
> days.
>
> Good week-end to all of you,
> Patrick
>
> ---
> List
59 matches
Mail list logo
