Christian Schmitz via curl-library in gmane.comp.web.curl.library (Sun,
19 Apr 2020 17:33:33 +0200):
>I looked into the pre-built CURL DLLs for Windows.
>But those I found on the website are all without Keberos.
>The download website doesn't list the features enabled for each build.
The curl by
Andreas Falkenhahn via curl-library in gmane.comp.web.curl.library (Sat,
19 Oct 2019 18:40:49 +0200):
>Please excuse this slightly off-topic question but I think this is the best
>place to ask about it ;)
>
>So unfortunately, my old test case HTTP server which sent HTTP responses
>without
>the
Hi Christoph and Daniel,
Christoph M. Becker (Wed, 11 Sep 2019 14:20:36 +0200):
>On 11.09.2019 at 13:36, Daniel Stenberg via curl-library wrote:
>
>> On Wed, 11 Sep 2019, Daniel Stenberg via curl-library wrote:
>>
Usng the winbuid system I am running into the error that nmake cannot
Daniel Stenberg (Wed, 11 Sep 2019 08:00:54 +0200 (CEST)):
> o curl_version_info: offer quic (and h3) library info [38]
> o see docs/KNOWN_BUGS (https://curl.haxx.se/docs/knownbugs.html)
Usng the winbuid system I am running into the error that nmake cannot
find vquic\ngtcp2.obj. I tried a lot of
Jan Ehrhardt via curl-library in gmane.comp.web.curl.library (Fri, 12
Apr 2019 23:07:42 +0200):
>PR will follow soon. I just wanted to check here first.
PR: https://github.com/curl/curl/pull/3772
>Daniel Stenberg via curl-library in gmane.comp.web.curl.library (Fri, 12
>Apr 2019 22:39
Daniel Stenberg via curl-library in gmane.comp.web.curl.library (Fri, 12
Apr 2019 22:39:37 +0200 (CEST)):
>On Fri, 12 Apr 2019, Jan Ehrhardt via curl-library wrote:
>
>> makefile.m32 and ./configure (when cross-compiling on *nix for Windows)
>> already support MultiSSL. How
makefile.m32 and ./configure (when cross-compiling on *nix for Windows)
already support MultiSSL. However the makefiles in /winbuild still
prohibit it. It requires a small adjustment to enable it there too:
https://github.com/Jan-E/cURL-winlibs/commit/3997fc006b3a3650f4b9bdb5b1f508ced04d00fb
See
Thomas Glanzmann via curl-library (Fri, 7 Sep 2018 12:57:24 +0200):
>Hello Jan,
>
>> x64 builds with OpenSSL just use the Windows certificate store. That
>> applies even to cross-compiled x64 builds. Try it yourself
>> https://phpdev.toolsforresearch.com/curl-mingw32-7.61.1.zip
>
>I tried, but
Daniel Stenberg via curl-library (Fri, 7 Sep 2018 09:30:11 +0200 (CEST)):
>I think it would be great to offer ability that to OpenSSL users on Windows.
It is already there in x64 builds of curl with OpenSSL!
--
Jan
---
Unsubscribe:
Juan Isoza via curl-library (Fri, 7 Sep 2018 08:57:48 +0200):
>But curl build for windows with openssl need a --insecure parameters or a
>custom certificate file.
x64 builds with OpenSSL just use the Windows certificate store.
That applies even to cross-compiled x64 builds.
Try it yourself
Jan Ehrhardt via curl-library (Sun, 26 Aug 2018 16:03:16 +0200):
>Daniel Jelinski via curl-library (Sun, 26 Aug 2018 09:09:58 +0200):
>>added 100ms: original 310kB/sec, patched 9900kB/sec
>
>Impressive results!
Do you have a compiled version somewhere?
I tried to build my own wit
Jan Ehrhardt via curl-library (Sun, 26 Aug 2018 16:28:47 +0200):
>Daniel Jelinski via curl-library (Sun, 26 Aug 2018 09:09:58 +0200):
>>The patched version is CPU-bound on lower latencies; when the latency
>>goes higher, SSH window becomes the limiting factor. I read that HPN
Daniel Jelinski via curl-library (Sun, 26 Aug 2018 09:09:58 +0200):
>The patched version is CPU-bound on lower latencies; when the latency
>goes higher, SSH window becomes the limiting factor. I read that HPN
>SSH should do better on high latency links, didn't try it out.
A lot of PR's for
Daniel Jelinski via curl-library (Sun, 26 Aug 2018 09:09:58 +0200):
>added 100ms: original 310kB/sec, patched 9900kB/sec
Impressive results!
>The patched version is CPU-bound on lower latencies; when the latency
>goes higher, SSH window becomes the limiting factor. I read that HPN
>SSH should do
Daniel Jelinski via curl-library (Sun, 26 Aug 2018 01:07:14 +0200):
>sob., 11 sie 2018 o 01:05 Daniel Stenberg napisa?(a):
>> It would require that libssh2 provides such an API, which it currently
>> doesn't
>> (and I don't know anyone working on it).
>
>Sent a PR to libssh2 for that:
Jan Ehrhardt via curl-library (Wed, 15 Aug 2018 22:51:34 +0200):
>Network connection: about 200 Mbits/s up, 200ms latency (speedtest.net)
>Test file: 178 MB mp4
>Protocol: sftp
>
>iPad app 32 KB libssh2 buffer: 2147 seconds
>iPad app 320 KB libssh2 buffer: 737 seconds
>File
Daniel Stenberg via curl-library (Tue, 14 Aug 2018 09:39:21 +0200 (CEST)):
>I think its time we run some tests in an orderly fashion with different upload
>buffer sizes and collect some numbers...
Feedback on some informal upload tests from Phoenix, Arizona to Amsterdam, NL.
High speed
Daniel Stenberg via curl-library (Tue, 14 Aug 2018 12:02:46 +0200
(CEST)):
> Size Seconds Improvement
>
> 16 KB2.522-
> 64 KB1.281x 1.97
> 128 KB 1.095x 2.30
> 256 KB 0.938x 2.69
> 512 KB 0.860x 2.93
Thanks for the stats. It indicates that my choice
Daniel Stenberg via curl-library (Tue, 14 Aug 2018 09:39:21 +0200
(CEST)):
>I think its time we run some tests in an orderly fashion with different upload
>buffer sizes and collect some numbers...
I did not test if there is a difference on *nix. Did you? Anyway, I
agree with the fact that some
Daniel Stenberg via curl-library (Mon, 13 Aug 2018 23:37:56 +0200
(CEST)):
>On Mon, 13 Aug 2018, Jan Ehrhardt via curl-library wrote:
>
>> Daniel Stenberg (Thu, 9 Aug 2018 16:55:38 +0200 (CEST)):
>> -#define UPLOAD_BUFSIZE CURL_MAX_WRITE_SIZE
>> +#define UPLOAD_BUFSIZE
Daniel Jelinski via curl-library (Tue, 7 Aug 2018 23:11:25 +0200):
>I recently started using HTTPS functionality with libcurl + openSSL; I
>noticed that by default this combo does not use Windows certificates,
>but instead wants to load them from CA bundle.
I happened to notice that recent X64
Daniel Stenberg (Thu, 9 Aug 2018 16:55:38 +0200 (CEST)):
-#define UPLOAD_BUFSIZE CURL_MAX_WRITE_SIZE
+#define UPLOAD_BUFSIZE (512*1024)
@Daniel Stenberg: is there a reason that is stopping you from changing
this in curl?
--
Jan
---
Daniel Stenberg via curl-library (Thu, 9 Aug 2018 16:55:38 +0200
(CEST)):
>-#define UPLOAD_BUFSIZE CURL_MAX_WRITE_SIZE
>+#define UPLOAD_BUFSIZE (512*1024)
This extra patch also had major speed improvements for Daniel Jelinski's
testcurl.bat. I have now included a fully static
Daniel Jelinski via curl-library (Fri, 10 Aug 2018 22:59:22 +0200):
>Ok, so let's put Linux to a test.
Reality check from a CentOS 6 machine
% Total% Received % Xferd Average Speed TimeTime Time Current
Dload Upload Total SpentLeft
Jan Ehrhardt via curl-library (Fri, 10 Aug 2018 17:25:51 +0200):
>running curl-mingw64 sftp
> % Total% Received % Xferd Average Speed TimeTime Time Current
> Dload Upload Total SpentLeft Speed
>100 274M0 0 100 274M
Jan Ehrhardt via curl-library (Fri, 10 Aug 2018 03:29:21 +0200):
>Gisle Vanem via curl-library (Thu, 9 Aug 2018 18:31:12 +0200):
>>Jan Ehrhardt wrote:
>>
>>>> Wow dude! 2 times faster than FileZilla now.
>>>>
>>>> Time decreased from 33.153s
Gisle Vanem via curl-library (Thu, 9 Aug 2018 18:31:12 +0200):
>Jan Ehrhardt wrote:
>
>>> Wow dude! 2 times faster than FileZilla now.
>>>
>>> Time decreased from 33.153s to 6.4 sec (same random 10 MByte file).
>>> Versus approx. 5.3 sec for curl/FTP.
>>
>> Using SFTP?
>
>Yes:
>curl.exe -k -#
Gisle Vanem via curl-library (Thu, 9 Aug 2018 17:48:49 +0200):
>Daniel Stenberg wrote:
>
>> /* The upload buffer size, should not be smaller than CURL_MAX_WRITE_SIZE,
>> as
>> it needs to hold a full buffer as could be sent in a write callback */
>> -#define UPLOAD_BUFSIZE
Daniel Stenberg via curl-library (Thu, 9 Aug 2018 16:55:38 +0200 (CEST)):
>On Thu, 9 Aug 2018, Jan Ehrhardt via curl-library wrote:
>
>> curl plain ftp patched 41 seconds
>> curl patched sftp 1925 seconds
>
>Oh what a sad number there... =(
>
>A quick lit
Gisle Vanem via curl-library (Thu, 9 Aug 2018 13:51:50 +0200):
>Jan Ehrhardt wrote:
>
>>> 33.153s vs 5.4s for a 10 MByte file.
>>
>> Did you time how long Filezilla takes for the same action? Filezilla
>> squeezes quite a lot over sftp-connections...
>
>11.4 sec!!
snip
>I must be using the wrong
Gisle Vanem via curl-library (Thu, 9 Aug 2018 01:42:18 +0200):
>Jan Ehrhardt wrote:
>
>> I ended up with a Windows port of lftp, launched from a bash script. Curl
>> sftp
>> did resume, but was terribly slow.
>
>I also just tested with 'curl sftp//:' with the latest libssh2
>and the new
31 matches
Mail list logo
