libcurl development talk. How to program using libcurl, and how to develop libcurl further

Yang Tse | 4 Jul 2012 12:45

[STEP 3] SSPI/Schannel string literals voting process

Hi friends,

[STEP 2] of this process has resulted in the following candidate lists.

Two candidates for the [STEP 3] Version_Literal voting:

[Version_Literal="Schannel"]
[Version_Literal="WinSSL"]

Two candidates for the [STEP 3] Config_Literal voting:

[Config_Literal="schannel"]
[Config_Literal="winssl"]

[STEP 3] of this voting process starts right now and will end at
00:00:01 GMT of July 9 2012 as previously indicated in
http://curl.haxx.se/mail/lib-2012-06/0300.html

In this last voting round, anyone voting must vote _one_
Version_Literal option and _one_ Config_Literal option.

In order to vote, reply to this thread and provide or quote in
message's body one Version_Literal option out of the two listed above
and one Config_Literal option out of the two also listed above.

If any message contains more than one vote for a single option, whole
message will be invalidated and considered fully ineffective.

Don't risk your vote being invalidated providing more info than what
is required on this thread. In case of doubt, start a new thread with

(Continue reading)

headers

Guenter | 4 Jul 2012 13:23

Re: [STEP 3] SSPI/Schannel string literals voting process

Am 04.07.2012 12:45, schrieb Yang Tse:
> [STEP 2] of this process has resulted in the following candidate lists.
>
> Two candidates for the [STEP 3] Version_Literal voting:
>
> [Version_Literal="Schannel"]
> [Version_Literal="WinSSL"]
>
> Two candidates for the [STEP 3] Config_Literal voting:
>
> [Config_Literal="schannel"]
> [Config_Literal="winssl"]
>
> [STEP 3] of this voting process starts right now and will end at
> 00:00:01 GMT of July 9 2012 as previously indicated in
> http://curl.haxx.se/mail/lib-2012-06/0300.html
>
> In this last voting round, anyone voting must vote _one_
> Version_Literal option and _one_ Config_Literal option.
my vote:
[Version_Literal="WinSSL"]
[Config_Literal="winssl"]

Gün.

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html

(Continue reading)

headers

Marc Hoersken | 4 Jul 2012 13:49

Re: [STEP 3] SSPI/Schannel string literals voting process

[Version_Literal="WinSSL"]
[Config_Literal="winssl"]

2012/7/4 Yang Tse <yangsita <at> gmail.com>
>
> Hi friends,
>
> [STEP 2] of this process has resulted in the following candidate lists.
>
> Two candidates for the [STEP 3] Version_Literal voting:
>
> [Version_Literal="Schannel"]
> [Version_Literal="WinSSL"]
>
> Two candidates for the [STEP 3] Config_Literal voting:
>
> [Config_Literal="schannel"]
> [Config_Literal="winssl"]
>
> [STEP 3] of this voting process starts right now and will end at
> 00:00:01 GMT of July 9 2012 as previously indicated in
> http://curl.haxx.se/mail/lib-2012-06/0300.html
>
> In this last voting round, anyone voting must vote _one_
> Version_Literal option and _one_ Config_Literal option.
>
> In order to vote, reply to this thread and provide or quote in
> message's body one Version_Literal option out of the two listed above
> and one Config_Literal option out of the two also listed above.
>

(Continue reading)

headers

Robert Bednar | 5 Jul 2012 23:06

Handling Multi-URL transfers with Failed Authentication


Sorry if this isn't going through official channels.  I'll strive to find the official forum for such
questions in the future.
I have some systems which have a painfully slow connection due to reverse DNS restrictions I have no control over.

I was performing discreet transfers of a dozen or so files - attempting an ftp transfer on each file one at a
time and checking the exit code. 
If run as "separate" Curl statements, each one required the 30-second penalty on reverse DNS. 
To get around the reverse DNS bottle neck I "stacked up" all my files into a single multi file transfer.  This
awesome.   I did presume it would add extra difficulty checking the return code/s ….but really…my only
real problem is username and password credentials.

My curl statement is something like this…

curl -u username:password 
ftp://192.168.123.1//home/mydir/{onefile,twofile,threefile,fourfile}  -O -O -O 

The problem is that if my username and password credentials fail… curl tries each file subsequently with
the same username and password that failed the first time.   This wouldn't normally be an issue except it
takes about 30 seconds to "connect" to the ftp server.  Since the connection is ultimately "refused"  I wait
30 seconds for EACH file in the multi-file request before my calling script gets a return code..and calls
someone a bonehead for supplying the wrong password.  This time can really add up. 

I'd like curl to "understand" that retrying the same rejected username and password on subsequent
multi-file requests isn't going to work - and exit pronto. 

R. Bednar
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html

(Continue reading)