On Tue, 7 May 2013, Mel Smith wrote:
Please don't top-post.
Altho I've got 'git' loaded on my Win XP Pro (s3) (sp3) ,
unfortunately, I've never used it.
So, I guess I'm outa-luck :(
You're not "out of luck". You can still:
1 - learn how to use git, which really is a useful skill t
Hi Mel,
On Tue, 7 May 2013, Daniel Stenberg wrote:
> > So, I guess I'm outa-luck :(
>
> You're not "out of luck". You can still:
>
> 1 - learn how to use git, which really is a useful skill these days and
the
> rudimentary commands are easy
You might like to take a look at TortoiseGit
On Tuesday, May 07, 2013 23:44:12 Daniel Stenberg wrote:
> On Tue, 7 May 2013, David Strauss wrote:
> >> What about using PR_INTERVAL_NO_WAIT instead of -1?
> >
> > I'm not sure there's a way for that to work efficiently without waiting
> > for
> > an event from NSS, if that's possible.
>
> That'
On Wed, 8 May 2013, Kamil Dudka wrote:
So are the NSS recv/send functions. Only the handshake still blocks with
NSS. I guess that David needs the following fix:
https://github.com/bagder/curl/commit/9d0af301
Ah yes, that might be it.
But don't you also agree that PR_INTERVAL_NO_WAIT is mor
On Tue, 7 May 2013, Alex Loukissas wrote:
Yes rather strange behavior, although it's not very frequent. Do you perhaps
have a hunch on anything I might have missed in the way I'm using curl_multi
interface?
Nothing you can do with the API should ever cause such a problem! So no, I
can't thin
- Original Message -
From: "Daniel Stenberg"
To: "libcurl development"
Sent: Wednesday, May 08, 2013 2:04 AM
Subject: Re: [bagder/curl] 8ec2cb5544 WIN32 MemoryTracking
On Tue, 7 May 2013, Mel Smith wrote:
Please don't top-post.
Altho I've got 'git' loaded on my Win XP Pro (s3) (s
> Date: Tue, 7 May 2013 23:52:19 +0200 (CEST)
> From: Daniel Stenberg
> To: libcurl development
> Subject: Re: Curl_resolv_timeout crash
> Message-ID:
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
>
> On Tue, 7 May 2013, Pankaj Takawale wrote:
>
> > libcurl: 7.21.4 (no threaded res
On IOS I have verified that the crash occurs on 7.28.1 if you do not set
NOSIGNAL
From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of
Pankaj Takawale
Sent: Wednesday, May 08, 2013 10:31 AM
To: curl-library@cool.haxx.se
Subject: Re: Curl_resolv_timeout crash
Date: Tue, 7
On Wed, May 8, 2013 at 5:15 AM, Daniel Stenberg wrote:
> But don't you also agree that PR_INTERVAL_NO_WAIT is more suitable than -1
> for the PR_Recv timeout parameter?
Summarizing my RHBZ comment [1], the timeout value seems completely
unused in the main send and receive functions if the non-blo
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 512 577 5827 [mobile]
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 [mobile]
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 */
if(SSL_
Thanks for the clarification, Daniel. From what I understood I think
it would make sense to copy the SSL session information from the
original easy handle into the spare closure handle, just like
Vuurvlieg suggested. The SSL session information may be considered
part of the connection state since i
2013/5/7 Daniel Stenberg :
> Just to clarify: we can close #1219 now then?
>
> https://sourceforge.net/p/curl/bugs/1219/
Yes, since my commit fixes the invalid memory access which leads to the crash.
---
List admin: http://cool.haxx.
I dont have any proposed fixes
--
Arunav Sanyal
4th year undergraduate student
B.E (Hons) Computer Science
BITS Pilani K.K Birla Goa Campus
---
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.s
I do understand the problem though. It seems curl behaves as a thin
client(exactly how browsers behave) when it comes to negotiate
authentication. In case of kerberos(one of the mechanisms supported by
negotiate) when a browser authenticates via negotiate, it never sets the
server name. What it doe
16 matches
Mail list logo
