Todd comments

Results 111 comments of


                                            Todd

userpwd words but setting username and password individually doesn't, hmm

Yeah, it was probably a mistake of mine to introduce .username and .password when there was already a userpwd... The .username and .password use a newer libcurl API... I'll try...

URIs with UTF-8 chars

it looks like curl_easy_escape might be causing your issue... see this: http://curl.haxx.se/libcurl/c/curl_easy_escape.html - in some case we use the older api

It looks like this might just be how libcurl works... see this example: ``` curl -I "http://%E3%90%87%E5%8C%82.sl.pt" HTTP/1.0 302 Found Date: Fri, 18 Mar 2011 02:53:05 GMT Server: Apache/1.3.41 (Unix)...

URIs with UTF-8 chars

Okay I might need more info about this, it looks like this definitely work in libcurl https://gist.github.com/875541 is it not working in curb?

Curl::Easy seems to have a limit for CURLOPT_INFILESIZE in Curl::Easy#http_put

``` curl_easy_setopt(curl, CURLOPT_INFILESIZE, FIX2LONG(size)); ``` ?

Curl::Easy seems to have a limit for CURLOPT_INFILESIZE in Curl::Easy#http_put

check my latest commit

warning: Possibly lost track of Curl::Easy VALUE, it may not be reclaimed by GC

I modified you script slightly to get it to run https://gist.github.com/751155 i'm not seeing the warning you were getting... it is a fairly harmless warning - it just means when...

warning: Possibly lost track of Curl::Easy VALUE, it may not be reclaimed by GC

yeah, it's definitely valid - i've also spotted it a few times... i added that report because I figured it could be possible... so i 'll keep this ticket open...

Segmentation fault when adding Curl::Easy instances to a Curl::Multi

Do you have a sample use case?

Segmentation fault when adding Curl::Easy instances to a Curl::Multi

Ilya, I'm going to use your suggest of the first access on a my 64 box and see if i can reproduce...