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
(please don't top-post)
On May 28, 2013, at 10:56 AM, Arjun SM wrote:
> Thanks for clearing the confusion here. Obviously i am linking to the
> libcurl.dylib which is Mac OS X provided.
>
> For now what would be the best solution so as to overcome the hang issue?
> Should i build the curl on
Thanks for clearing the confusion here. Obviously i am linking to
the*libcurl.dylib
*which is Mac OS X provided.
For now what would be the best solution so as to overcome the hang issue?
Should i build the curl on my own for Mac OS X 10.8.3 Mountain Lion and
link the same with my daemon ?
thanks,
On 05/28/2013 08:17 AM, Kim Vandry wrote:
Ben Greear wrote:
I'm just now doing some more testing on my trees, and I'm getting
trouble just resolving names
with no special configuration. I'm going to fix this one way or
another and will
post some patches for review when I get them in order...
Ben Greear wrote:
>I'm just now doing some more testing on my trees, and I'm getting
>trouble just resolving names
>with no special configuration. I'm going to fix this one way or
>another and will
>post some patches for review when I get them in order
Hi Ben,
I was wondering if you had m
On Tue, 28 May 2013, Arjun SM wrote:
Also i dug deep into the functions from the sample, i found out that
*Curl_resolver_wait_resolv() function should not be used *since using this
risk getting the multi interface to "hang". This function is getting called
from Curl_do_perform()
If your libc
Thanks for the reply.
I haven't tried downloading/building a newer version of libCurl. I will try
that.
Also i dug deep into the functions from the sample, i found out that
*Curl_resolver_wait_resolv()
function should not be used *since using this risk getting the multi
interface to "hang".
This
On Mon, May 27, 2013 at 09:27:49PM -0500, David Strauss wrote:
> On Mon, May 27, 2013 at 11:33 AM, Mohammad_Alsaleh wrote:
> > Am I doing something wrong?
>
> Instead of expecting it as a header, you should read the code using
> curl_easy_getinfo() with CURLINFO_RESPONSE_CODE [1], assuming
> curl
https://sourceforge.net/p/curl/feature-requests/70/
>From IRC:
Bagder: would you at all be interested in a patch that implements Digest
Auth with qop=auth-int, which does so in an unorthodox manner?
Nach: I think it depends on what exactly that means! =)
Bagder: one would need to pass the MD5
https://sourceforge.net/p/curl/feature-requests/70/
>From IRC:
Bagder: would you at all be interested in a patch that implements Digest
Auth with qop=auth-int, which does so in an unorthodox manner?
Nach: I think it depends on what exactly that means! =)
Bagder: one would need to pass the MD5
10 matches
Mail list logo
