Re: relative performance

> Slow enough for what? I agree that if we run the tests over an actual > physical > network, a system with a fast enough CPU will saturate the network and then > it > mostly won't matter how fast or not curl is. > > For this kind of test to be sensible, we need to make sure to either have a

RE: Connection to file server disconnected while file transfer is in progress

On Thu, 26 Aug 2021, vaibhav.taksale--- via curl-library wrote: Regarding disconnection, here is code flow - 1. Authentication to server successful. 2. Opening data channel for File download from server 3. after 2 minutes, connection timed out. How does it "time out" ? What does it mean, exact

RE: Connection to file server disconnected while file transfer is in progress

sday, 25 August, 2021 12:04 To: vaibhav.taksale--- via curl-library Cc: Taksale Vaibhav (M) Subject: RE: Connection to file server disconnected while file transfer is in progress On Wed, 25 Aug 2021, vaibhav.taksale--- via curl-library wrote: > [Vaibhav] Libcurl version 7.58 Used on Embedded

Re: relative performance

On Wed, 25 Aug 2021, XSLT2.0 via curl-library wrote: Summary : IMHO the important thing is to test on a "slow enough" machine, assuming the main measure you want is "elapsed". Slow enough for what? I agree that if we run the tests over an actual physical network, a system with a fast enough C

Re: relative performance

On Wed, Aug 25, 2021 at 12:33 bch wrote: > > > On Wed, Aug 25, 2021 at 00:35 Daniel Stenberg via curl-library < > curl-library@cool.haxx.se> wrote: > >> On Tue, 24 Aug 2021, Ben Greear via curl-library wrote: >> >> > What is your network-under-test in this case? >> >> Not sure. >> >> I hope to co

Re: relative performance

On Wed, Aug 25, 2021 at 00:35 Daniel Stenberg via curl-library < curl-library@cool.haxx.se> wrote: > On Tue, 24 Aug 2021, Ben Greear via curl-library wrote: > > > What is your network-under-test in this case? > > Not sure. > > I hope to come up with a way where the network and exact server aren't

Re: relative performance

Hello curl team, Summary : IMHO the important thing is to test on a "slow enough" machine, assuming the main measure you want is "elapsed". A Raspberry Pi 4 is a good candidate, and quite cheap (you don't need the 8GB RAM model to run curl!). Alternatives are of course using a much faster networ

Re: relative performance

On Tue, 24 Aug 2021, Ben Greear via curl-library wrote: What is your network-under-test in this case? Not sure. I hope to come up with a way where the network and exact server aren't terribly important as long as they perform roughly the same on repeated runs. It would need some experimenti

RE: Connection to file server disconnected while file transfer is in progress

On Wed, 25 Aug 2021, vaibhav.taksale--- via curl-library wrote: [Vaibhav] Libcurl version 7.58 Used on Embedded Linux platform on ar758x board. This should come as no surprise but of course my first recommendation will be to upgrade your libcurl to a recent release as whatever problem you exp

RE: Connection to file server disconnected while file transfer is in progress

small stand-alone example program that reproduces the > problem? [Vaibhav] This is download. I will provide small code writeup. Regards, Vaibhav -Original Message- From: Daniel Stenberg Sent: Tuesday, 24 August, 2021 20:57 To: vaibhav.taksale--- via curl-library Cc: Taksale Vai

Re: relative performance

> Am 24.08.2021 um 17:20 schrieb Daniel Stenberg via curl-library > : > > Hi all, > > For a long time I've wanted to get something done that allows us to compare > curl's relative performance. Ideally something we can run every once in a > while to compare that nothing major has turned sour

Re: relative performance

On 8/24/21 8:20 AM, Daniel Stenberg via curl-library wrote: Hi all, For a long time I've wanted to get something done that allows us to compare curl's relative performance. Ideally something we can run every once in a while to compare that nothing major has turned sour without us being aware of

Re: Connection to file server disconnected while file transfer is in progress

On Tue, 24 Aug 2021, vaibhav.taksale--- via curl-library wrote: Connection to file server disconnected while file transfer is in progress CURL does not get this disconnection response and will continue to wait for file transfer. That's a bug then. Either in your code or in libcurl. Which lib

Re: Assistance building curl 7.77.0 with OpenSSL 3.0

I saw that and it is annoying. Trivial to just move the resultant target libs around after install however. Just be careful of the RPATH/RUNPATH data in your final ELF objects. >> (and no, I don't know why they decided this). Line forms on the left behind me. I have no clue w

RE: Assistance building curl 7.77.0 with OpenSSL 3.0

On August 21, 2021, Daniel Stenberg wrote: >On Sat, 21 Aug 2021, Randall S. Becker wrote: > >> The OpenSSL build is definitely 64 bit - I know because I did the >> build/install about 2 weeks ago. If I leave off the -Wlp64, the linker >> complains about mixing 64 (openssl) and 32 models (curl) duri

RE: Assistance building curl 7.77.0 with OpenSSL 3.0

On Sat, 21 Aug 2021, Randall S. Becker wrote: The OpenSSL build is definitely 64 bit - I know because I did the build/install about 2 weeks ago. If I leave off the -Wlp64, the linker complains about mixing 64 (openssl) and 32 models (curl) during the configure phase claiming it can't find open

Re: configure options for various libcurl builds

On Sat, 21 Aug 2021, Anmol Mishra via curl-library wrote: Could there be some guidance about a simple libcurl static build for For configure builds, both a shared and a static libcurl version are built. SMTP is enabled by default. -- / daniel.haxx.se | Commercial curl support up to 24x7

Re: configure options for various libcurl builds

On Sat, Aug 21, 2021 at 05:42:47PM +, Anmol Mishra via curl-library wrote: > Could there be some guidance about a simple libcurl static build for Static building is tricky because the entire chain of static dependencies resulting from all libcurl dependencies needs to be added to the final lin

RE: Assistance building curl 7.77.0 with OpenSSL 3.0

On August 21, 2021 5:35 AM, Daniel Stenberg wrote: >On Fri, 20 Aug 2021, Randall S. Becker via curl-library wrote: > >> My latest configure command for OpenSSL 3.0 is: >> >> CFLAGS="-c99" CPPFLAGS="-D_XOPEN_SOURCE_EXTENDED=1 -Wlp64 -WIEEE_float >> -I/usr/local-ssl3.0/openssl/include" LDFLAGS="-L/us

RE: Assistance building curl 7.77.0 with OpenSSL 3.0

On August 21, 2021 5:35 AM, Daniel Stenberg wrote: >On Fri, 20 Aug 2021, Randall S. Becker via curl-library wrote: > >> My latest configure command for OpenSSL 3.0 is: >> >> CFLAGS="-c99" CPPFLAGS="-D_XOPEN_SOURCE_EXTENDED=1 -Wlp64 -WIEEE_float >> -I/usr/local-ssl3.0/openssl/include" LDFLAGS="-L/us

Re: No curl_*_strerror() for CURLUcode

> Nothing special, no. A pull-request is perfect and we take it from there. Here it is: https://github.com/curl/curl/pull/7605 --- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquett

Re: Assistance building curl 7.77.0 with OpenSSL 3.0

On Fri, 20 Aug 2021, Randall S. Becker via curl-library wrote: My latest configure command for OpenSSL 3.0 is: CFLAGS="-c99" CPPFLAGS="-D_XOPEN_SOURCE_EXTENDED=1 -Wlp64 -WIEEE_float -I/usr/local-ssl3.0/openssl/include" LDFLAGS="-L/usr/local-ssl3.0/lib" conf_script_floss_cc --with-ssl=/usr/loc

Re: CURLE_COULDNT_RESOLVE_HOST from CURLU API on https://www.google.com

Perfect, that's it! Thanks, Samuel Marks Charity | consultancy | open-source | LinkedIn On Fri, Aug 20, 2021 at 3:51 PM Daniel Stenberg wrote: > On Fri, 20 Aug 2021, Samuel

Re: CURLE_COULDNT_RESOLVE_HOST from CURLU API on https://www.google.com

On Fri, 20 Aug 2021, Samuel Marks via curl-library wrote: curl_easy_setopt(curl, CURLOPT_URL, urlp); From the CURLOPT_URL man page: Pass in a pointer to the URL to work with. The parameter should be a char * to a null-terminated string which must be URL-encoded You seem to have intended

Re: libcurl.a linker errors on XCode

. From: Daniel Stenberg Sent: Thursday, 19 August 2021 9:19 AM To: Anmol Mishra via curl-library Cc: Anmol Mishra Subject: Re: libcurl.a linker errors on XCode On Thu, 19 Aug 2021, Anmol Mishra via curl-library wrote: > That makes sense. Is there a list

Re: libcurl.a linker errors on XCode

On Thu, 19 Aug 2021, Anmol Mishra wrote: Using these flags allows for a build - -L/usr/local/Cellar/curl/7.78.0/lib -lcurl The problem is that -lcurl is probably bringing in the default system lib. And that is not something I want. When you build your application you use a linker. If that l

Re: libcurl.a linker errors on XCode

On Thu, 19 Aug 2021, Anmol Mishra wrote: Intuitively, these extra dependencies seems wrong. If I build a static version of a lib, it should not depend on a shared lib. You build a static version of libcurl. That's static. You then need to make sure to use whatever you want from the dependenci

Re: libcurl.a linker errors on XCode

. From: Daniel Stenberg Sent: Thursday, 19 August 2021 9:19 AM To: Anmol Mishra via curl-library Cc: Anmol Mishra Subject: Re: libcurl.a linker errors on XCode On Thu, 19 Aug 2021, Anmol Mishra via curl-library wrote: > That makes sense. Is there a list of dependenc

Re: libcurl.a linker errors on XCode

On Thu, 19 Aug 2021, Anmol Mishra via curl-library wrote: That makes sense. Is there a list of dependencies somewhere ? It depends entirely on your specific build. "sh curl-config --libs" should list them after a build. -- / daniel.haxx.se | Commercial curl support up to 24x7 is available

Re: libcurl.a linker errors on XCode

That makes sense. Is there a list of dependencies somewhere ? From: Daniel Stenberg Sent: Thursday, 19 August 2021 9:10 AM To: Anmol Mishra via curl-library Cc: Anmol Mishra Subject: Re: libcurl.a linker errors on XCode On Thu, 19 Aug 2021, Anmol Mishra via

Re: libcurl.a linker errors on XCode

On Thu, 19 Aug 2021, Anmol Mishra via curl-library wrote: I built a homebrew libcurl in a custom dir. The project is linking against this custom lib. I am getting 200+ linker errors. As far as I know, I followed the FAQ. I'm missing something very basic. It looks like you're building and usin

Re: No curl_*_strerror() for CURLUcode

On Fri, 13 Aug 2021, Gleb Ivanovsky wrote: It is my first time contributing to libcurl. Are there additional steps required or do I just create a pull request? Nothing special, no. A pull-request is perfect and we take it from there. Perhaps eye through this first: https://curl.se/dev/contrib

Re: No curl_*_strerror() for CURLUcode

On Fri, Aug 13, 2021 at 12:00 PM Daniel Stenberg wrote: > > On Fri, 13 Aug 2021, Gleb Ivanovsky via curl-library wrote: > > > Would be nice to have something like: > > const char *curl_url_strerror(CURLUcode errornum); > > I agree. It would be consistent with how the API works generally. > > Do yo

Re: No curl_*_strerror() for CURLUcode

On Fri, 13 Aug 2021, Gleb Ivanovsky via curl-library wrote: Would be nice to have something like: const char *curl_url_strerror(CURLUcode errornum); I agree. It would be consistent with how the API works generally. Do you want to work on it and make it happen? -- / daniel.haxx.se | Commer

Re: External WS library?

On Thu, 12 Aug 2021, Felipe Gasper via curl-library wrote: Regarding the plan to add WebSocket to curl, would it be useful to consider, instead of writing a new implementation, incorporating an existing library? Yes, I think that's a very sensible way to imlement the discussed API and matches

Re: Question on CURLINFO_SPEED_DOWN/UPLOAD when paused/resumed

Great, thanks for verifying, Much appreciated, -Josh On Thu, Aug 12, 2021 at 6:11 AM Daniel Stenberg wrote: > On Fri, 6 Aug 2021, Joshua Harlow via curl-library wrote: > > > When pausing and resuming I was noticing that CURLINFO_SPEED_UPLOAD and > > CURLINFO_SPEED_DOWNLOAD and its counters/tim

RE: more WebSockets

by implementations to signal > something without negotiating an extension? In general, all extensions must be negotiated, but I saw cases when some WS client/server implementations used reserved control opcodes for their proprietary communication. I guess they used it for some kind of "r

Re: Question on CURLINFO_SPEED_DOWN/UPLOAD when paused/resumed

On Fri, 6 Aug 2021, Joshua Harlow via curl-library wrote: When pausing and resuming I was noticing that CURLINFO_SPEED_UPLOAD and CURLINFO_SPEED_DOWNLOAD and its counters/timers don't seem to reset (which may just be how it is) and from looking at the progress.c code I think this is what is happ

Re: more WebSockets

uot;. Commenting myself: But if one wants to disregard all this "future proof" and "maybe one day multiplexing" thing in the standard, a re-assembly of fragments into "messages" seems useful for an application. > >> Am 12.08.2021 um 09:24 schrieb Daniel S

Re: more WebSockets

One thing from rfc6455, ch. 5.4: "An intermediary MUST NOT change the fragmentation of a message if any reserved bit values are used and the meaning of these values is not known to the intermediary." which I read as: if you want to use libcurl as an intermediary, it needs to expose t

RE: more WebSockets

On Thu, 12 Aug 2021, Daniel Stenberg via curl-library wrote: Should we just impose our own maximum size and have applications raise it when needed? Answering myself. =) Ok, I'm convinced we should make the API able to provide full messages. I'll adjust acccording. -- / daniel.haxx.se |

Re: more WebSockets

On Thu, 12 Aug 2021, Weston Schmidt wrote: I'd like to add a flag to CURLOPT_WS_OPTIONS that tells curl if it should negotiate compression or not for easy & multi. I like the automatic response to pings & pongs by default. Perhaps another CURLOPT_WS_OPTIONS flag might disable the automatic r

RE: more WebSockets

On Wed, 11 Aug 2021, Dmitry Karpov via curl-library wrote: Thanks for the feedback, this is very helpful! From a brief look at the document, it looks like Curl will provide only WebSocket frame level of communication, so the client will have to implement full message assembling itself. If yo

Re: more WebSockets

>> Other websockets implementations are doing that then I presume? I'll only speak to my implementation ... I provided both a streaming interface and a block/message interface. The block/message is nice for small stuff if you know limits but, for all the reasons you point out, streaming through a

Re: more WebSockets

On Wed, 11 Aug 2021, Felipe Gasper wrote: When a single frame can be 61 bits large? (Of course I meant 63...) And thanks for this. As you know I'm a WebSockets rookie so I need and appricate pointers like this! I believe most implementations enforce a maximum message length. Mojolicious (

Re: more WebSockets

> On Aug 11, 2021, at 6:34 PM, Daniel Stenberg wrote: > > On Wed, 11 Aug 2021, Felipe Gasper wrote: > >> Why frame by frame? JS’s API only does full messages, and I think the RFC >> actually stipulates that. > > When a single frame can be 61 bits large? I believe most implementations enforce

RE: more WebSockets

Hi Daniel, From a brief look at the document, it looks like Curl will provide only WebSocket frame level of communication, so the client will have to implement full message assembling itself. Summarizing this approach, it seems that libcurl will provide the following: 1. WS handshake handling

Re: more WebSockets

On Wed, 11 Aug 2021, Felipe Gasper wrote: Why frame by frame? JS’s API only does full messages, and I think the RFC actually stipulates that. When a single frame can be 61 bits large? -- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support

Re: more WebSockets

> On Aug 11, 2021, at 17:46, Daniel Stenberg via curl-library > wrote: > > A single fragment can be 61 bits large and a message consists of multiple > such fragments: we must have an API that provides data piece by piece to the > applicaiton and signal the FIN when it arrives. Why frame by f

Re: Read from specified location

‐‐‐ Original Message ‐‐‐ On Monday, August 2nd, 2021 at 9:33 PM, Tomalak Geret'kal via curl-library wrote: > On 02/08/2021 16:01, jeev2000 via curl-library wrote: > >> hello, >> >> If accept ranges are not supported, how to seek and start a read from >> specific location. >> >> I am usi

Re: Read from specified location

On 02/08/2021 16:01, jeev2000 via curl-library wrote: > hello, > > If accept ranges are not supported, how to seek and start > a read from specific location. > > I am using Read callback using |CURLOPT_WRITEFUNCTION. I > don't see any option to be specified for reading from > specifed location. Eve

Re: [PATCH] docs: correct symbols-in-versions & doc mismatch for 7.16.4

On Fri, Jul 30 2021, Daniel Stenberg wrote: > On Fri, 30 Jul 2021, Ævar Arnfjörð Bjarmason via curl-library wrote: > >> These options introduced in 7.17.0 were documented in 9f44a9552 >> (Renamed several libcurl error codes[...], 2007-08-30) as being >> introduced in version 7.16.4, but as lookin

Re: [PATCH] docs: correct symbols-in-versions & doc mismatch for 7.16.4

On Fri, 30 Jul 2021, Ævar Arnfjörð Bjarmason via curl-library wrote: These options introduced in 7.17.0 were documented in 9f44a9552 (Renamed several libcurl error codes[...], 2007-08-30) as being introduced in version 7.16.4, but as looking at the 7.16.4 tag and tarball[1] reveals they weren't

Re: How to handle _wcsdup() memory allocation

On Thu, 29 Jul 2021, Jeff Mears via curl-library wrote: Another answer would be for libcurl to implement its own wcsdup, because it's just wcslen + Curl_cmalloc + memcpy. Not being a Windows guy at all, this seems like the most reasonable way that doesn't introduce a new API and make things w

Re: Killed!

Sounds like you are getting OOM-killed, check dmesg or /var/log/messages if there are ny info about OOM kicking in /HH Den lör 24 juli 2021 kl 09:22 skrev XSLT2.0 via curl-library < curl-library@cool.haxx.se>: > Hello, > > Have you heard of any instance when the use of libcurl would "kill" > -di

Re: 7.78.0: configure: tweak nghttp2 library name fix

On Wed, 21 Jul 2021, Christian Weisgerber via curl-library wrote: Similar variable manipulation elsewhere in configure.ac uses sed, so I suggest to use the same idiom here: Thanks, I made a PR out of your patch: https://github.com/curl/curl/pull/7472 -- / daniel.haxx.se | Commercial curl s

RE: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

ation/json\r\nContent-Length: 1471\r\n\r\n%s\r\n" -Original Message- From: curl-library [mailto:curl-library-boun...@cool.haxx.se] On Behalf Of Daniel F via curl-library Sent: Tuesday, July 20, 2021 3:22 AM To: libcurl development Cc: dan...@poradnik-webmastera.com Subject:

Re: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

library [mailto:curl-library-boun...@cool.haxx.se] ON BEHALF OF Zakrzewski, Jakub via curl-library SENT: Monday, July 19, 2021 2:38 AM TO: libcurl development CC: Zakrzewski, Jakub SUBJECT: Re: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_e

RE: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

er, which I hope I am doing it right but highly doubtful and need some guidance. -Original Message- From: Daniel Stenberg [mailto:dan...@haxx.se] Sent: Monday, July 19, 2021 5:26 PM To: Venkat Maddisetti via curl-library Cc: Venkat Maddisetti Subject: RE: How to authenticate when using

RE: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

On Mon, 19 Jul 2021, Venkat Maddisetti via curl-library wrote: Before coming here I realized curl_easy_setopt has no effect setting username and password CURLOPT_USERPWD, CURLOPT_USERNAME and CURLOPT_PASSWORD included ? "POST /emp/ HTTP/1.1 If you want HTTP, then using CONNECT_ONLY + send/

RE: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

rl-library-boun...@cool.haxx.se] On Behalf Of Zakrzewski, Jakub via curl-library Sent: Monday, July 19, 2021 2:38 AM To: libcurl development Cc: Zakrzewski, Jakub Subject: Re: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

Re: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

Dnia 2021-07-19, o godz. 03:38:27 Venkat Maddisetti via curl-library napisał(a): > To give some background, I am able to authenticate and able to work with the > box with the blocked call ( without CURLOPT_CONNECT_ONLY option) with no > control over the curl connection. The problem is, since the

Re: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv()

You have literally told curl to connect and do nothing else. BasicAuth is a part of HTTP protocol and done via HTTP headers which will not be send with CURLOPT_CONNECT_ONLY. If you want to continue using CURLOPT_CONNECT_ONLY, you'll have to do the HTTP part yourself. ___

Re: undefined symbol: curl_multi_poll

Date: Fri, 16 Jul 2021 15:27:36 -0700 From: Dan Fandrich To: curl-library@cool.haxx.se Subject: Re: undefined symbol: curl_multi_poll Message-ID: Content-Type: text/plain; charset=iso-8859-1 >Run "curl -V" to look at the versions you're running. It sounds like your curl &

Re: undefined symbol: curl_multi_poll

On Fri, Jul 16, 2021 at 05:14:54PM -0400, Steve Scott via curl-library wrote: > I am trying to install curl with libssh2 enabled. I am following this > tutorial: > Ubuntu: Fix Protocol "sftp" not supported or disabled in libcurl « Yousof > Kamal > (ykamal.com) > > I used the following command to

Re: Can I use curl_easy_setopt during curl_easy_perform.

On Mon, 12 Jul 2021, Wu Yuanshou via curl-library wrote: Shall I call curl_easy_setopt() during curl_easy_perform() ? It seems like we should not do this according to the document I can find.Instead , I shall quit from the curl_easy_perform() function , apply the setting via curl_easy_setopt()

Re: Recv failure error under censorship conditions

just fyi this is how the same request looks from here in Europe (added -v to show more verbose): henrik@ubuntu:~/utveckling/other/mdf_client$ curl -Iv google.com * Trying 172.217.20.46:80... * TCP_NODELAY set * Connected to google.com (172.217.20.46) port 80 (#0) > HEAD / HTTP/1.1 > Host: google

Re: Recv failure error under censorship conditions

As your own research shows they are most definitely filtering based on user-agent. Probably done in order to filter out access from various mobile phone apps. There could of course be other types of filters as well but your example clearly demonstrates the presence of a user-agent filter for web b

Re: Recv failure error under censorship conditions

On 15/07/2021 13:50, Gealber Morales via curl-library wrote: > > The curious thing is that I can access google from the > browser, and I tried another thing, I made the same > request changing the `User-Agent` to simulate the request > of a browser: [..] > In this case, I get the expected response

Re: Support_better_than_MD5_hostkey

> On 8 Jul 2021, at 14:05, Mats Lindestam via curl-library > wrote: > I am trying to implement support for SHA256 public keys. I have been able to > reach as far as the lib/vssh/libssh2.c file and the ssh_check_fingerprint > function. Now I have no idea on how to calculate the SHA156 public ke

Re: [PATCH] Revert "ftp: Expression 'ftpc->wait_data_conn' is always false"

On Wed, 7 Jul 2021, Jonathan Wernberg via curl-library wrote: I could not make a GitHub pull request at this point in time, I hope it is acceptable to send the patch this way instead. Thanks! I made a PR out of it: https://github.com/curl/curl/pull/7362 -- / daniel.haxx.se | Commercial cu

Re: SCHANNEL failing in 7.77 when it worked in 7.74

Are you using libcurl with http2 enabled? If so, this sounds exactly like the issue fixed in this change: https://github.com/curl/curl/pull/7138 I submitted that fix shortly after the 7.77 release. If this is indeed the solution to your problem, you will need to either wait for the 7.78 release, o

RE: curl websockets

at the protocol prescribes. Thanks, Dmitry Karpov -Original Message- From: Felipe Gasper Sent: Saturday, July 3, 2021 3:44 AM To: libcurl development Cc: Dmitry Karpov Subject: Re: curl websockets > On Jul 2, 2021, at 9:07 PM, Dmitry Karpov via curl-library > wrote: > >>

RE: curl websockets

e- From: curl-library On Behalf Of Daniel F via curl-library Sent: Saturday, July 3, 2021 4:56 AM To: libcurl development Cc: dan...@poradnik-webmastera.com Subject: Re: curl websockets W dniu 2021-07-03 12:36, Felipe Gasper via curl-library napisał(a): >> On Jul 2, 2021, at 7:47 PM

Re: curl websockets

> On Jul 3, 2021, at 7:55 AM, Daniel F via curl-library > wrote: > > W dniu 2021-07-03 12:36, Felipe Gasper via curl-library napisał(a): >>> On Jul 2, 2021, at 7:47 PM, Nicolas Mora via curl-library >>> wrote: > Alternatively, have separate curl_ws_send_text and curl_ws_send_binary

Re: curl websockets

W dniu 2021-07-03 12:36, Felipe Gasper via curl-library napisał(a): On Jul 2, 2021, at 7:47 PM, Nicolas Mora via curl-library wrote: Alternatively, have separate curl_ws_send_text and curl_ws_send_binary functions? That could certainly work and would save users sending text from having to se

Re: curl websockets

> On Jul 2, 2021, at 9:07 PM, Dmitry Karpov via curl-library > wrote: > >> could libcurl wait for all the fragmented messages to arrive, then concat >> them and serve the completed message to the calling application? > > I don't think it is possible in all the cases. WebSocket text/data messa

Re: curl websockets

> On Jul 2, 2021, at 7:47 PM, Nicolas Mora via curl-library > wrote: > >>> Alternatively, have separate curl_ws_send_text and curl_ws_send_binary >>> functions? >> That could certainly work and would save users sending text from having to >> set a "this is text" bit. My personal preference is

Re: curl websockets

> On Jul 2, 2021, at 5:53 PM, Daniel Stenberg wrote: > > On Fri, 2 Jul 2021, Felipe Gasper wrote: > >>> Or perhaps with the type and flags just made as a single bitmask. >> >> This will make it impossible to specify a continuation frame rather than a >> data frame. (Context: when a message i

RE: curl websockets

t: Friday, July 2, 2021 4:48 PM To: libcurl development Cc: Nicolas Mora ; Daniel Stenberg Subject: Re: curl websockets Le 2021-07-02 à 17 h 53, Daniel Stenberg via curl-library a écrit : >> >> This will make it impossible to specify a continuation frame rather >> than a data fr

Re: curl websockets

Le 2021-07-02 à 17 h 53, Daniel Stenberg via curl-library a écrit : This will make it impossible to specify a continuation frame rather than a data frame. (Context: when a message is fragmented, the message’s first frame is text/binary, and the latter ones are continuation.) "CURL_WS_MORE"

Re: curl websockets

On Fri, Jul 2, 2021 at 14:55 Daniel Stenberg via curl-library < curl-library@cool.haxx.se> wrote: > On Fri, 2 Jul 2021, Felipe Gasper wrote: > > >> Or perhaps with the type and flags just made as a single bitmask. > > > > This will make it impossible to specify a continuation frame rather than > a

Re: curl websockets

On Fri, 2 Jul 2021, Felipe Gasper wrote: Or perhaps with the type and flags just made as a single bitmask. This will make it impossible to specify a continuation frame rather than a data frame. (Context: when a message is fragmented, the message’s first frame is text/binary, and the latter o

Re: curl websockets

On Fri, 2 Jul 2021, Weston Schmidt wrote: I'm not sure who might be using that & yes it's 8 years old in a draft state. I mentioned it because it's one of the more extreme looking use cases. If we can support that type of extension via a planned interface then we've probably got a good API.

Re: curl websockets

I'm not sure who might be using that & yes it's 8 years old in a draft state. I mentioned it because it's one of the more extreme looking use cases. If we can support that type of extension via a planned interface then we've probably got a good API. On Fri, Jul 2, 2021 at 10:07 AM Felipe Gasper

Re: curl websockets

> On Jul 2, 2021, at 1:03 PM, Weston Schmidt > wrote: > > This extension concerns me as it renders the > curl_easy_ws_send()/recv() to not have value ... but as long as it > could be implemented using curl_easy_send()/recv() then I'm happy. > https://datatracker.ietf.org/doc/html/draft-ietf-hy

Re: curl websockets

I took the bitmask path for my implementation similar to what Daniel has proposed. I like the flexibility and clarity it offers. Something like this might work (they need better names probably): /* WS extension declarations as needed */ CURL_WS_COMPRESS(1 << 10) /* WS frame flags */ CURL_WS

Re: curl websockets

> On Jul 2, 2021, at 7:40 AM, Daniel Stenberg wrote: > > On Fri, 2 Jul 2021, Felipe Gasper wrote: > > Thanks! > >> The send interface could look much like curl_easy_send(): >> >> curl_ws_send( easy, buffer, buflen, &sent, enum curl_ws_message_type type, >> enum curl_ws_flags flags ) > > Or

Re: curl websockets

On Fri, 2 Jul 2021, Felipe Gasper wrote: Thanks! The send interface could look much like curl_easy_send(): curl_ws_send( easy, buffer, buflen, &sent, enum curl_ws_message_type type, enum curl_ws_flags flags ) Or perhaps with the type and flags just made as a single bitmask. Most WS librari

Re: curl websockets

> On Jul 2, 2021, at 4:33 AM, Daniel Stenberg via curl-library > wrote: > > On Thu, 1 Jul 2021, Weston Schmidt wrote: > >> I like the simplicity of the CURLOPT_CONNECT_ONLY=2L + ws:// or wss:// plan. >> >> If libcurl stops at the _The WebSocket Connection is Established_ point >> (https://da

Re: curl websockets

On Thu, 1 Jul 2021, Weston Schmidt wrote: I like the simplicity of the CURLOPT_CONNECT_ONLY=2L + ws:// or wss:// plan. If libcurl stops at the _The WebSocket Connection is Established_ point (https://datatracker.ietf.org/doc/html/rfc6455#page-20) when CURLOPT_CONNECT_ONLY=2L, then by definiti

Re: Access gmail with pycurl.

On Fri, Jul 2, 2021 at 12:16 PM Ray Satiro via curl-library wrote: > > On 6/29/2021 12:33 AM, Hongyi Zhao via curl-library wrote: > > On Tue, Jun 29, 2021 at 5:55 AM Daniel Stenberg wrote: > > On Sat, 26 Jun 2021, Hongyi Zhao via curl-library wrote: > > I noticed that libcurl, hence pycurl suppor

Re: Access gmail with pycurl.

On 6/29/2021 12:33 AM, Hongyi Zhao via curl-library wrote: On Tue, Jun 29, 2021 at 5:55 AM Daniel Stenberg wrote: On Sat, 26 Jun 2021, Hongyi Zhao via curl-library wrote: I noticed that libcurl, hence pycurl supports IMAP and IMAPS, so I want to know if I can use it to retrieve/remove emails

Re: curl websockets

I like the simplicity of the CURLOPT_CONNECT_ONLY=2L + ws:// or wss:// plan. If libcurl stops at the _The WebSocket Connection is Established_ point (https://datatracker.ietf.org/doc/html/rfc6455#page-20) when CURLOPT_CONNECT_ONLY=2L, then by definition that is only after the HTTP response 101 Upg

Re: curl websockets

On Wed, 30 Jun 2021, Weston Schmidt wrote: Maybe this is a misunderstanding on my part, but I think (and my testing seems to confirm) that CURLOPT_CONNECT_ONLY will stop at the first connection to the first server encountered. If you have some other http redirector in front of the ultimate se

Re: curl websockets

Thanks, Daniel. Maybe this is a misunderstanding on my part, but I think (and my testing seems to confirm) that CURLOPT_CONNECT_ONLY will stop at the first connection to the first server encountered. If you have some other http redirector in front of the ultimate server hosting the websocket, or

Re: curl websockets

On Thu, 24 Jun 2021, Weston Schmidt via curl-library wrote: This has been good feedback, thank you all. I'm going to work on writing up what has been covered into a proposal here: https://github.com/schmidtw/curl-websocket-proposal I created a "home" for the WebSockets brain-storming in curl

Re: Access gmail with pycurl.

On Tue, Jun 29, 2021 at 5:55 AM Daniel Stenberg wrote: > > On Sat, 26 Jun 2021, Hongyi Zhao via curl-library wrote: > > > I noticed that libcurl, hence pycurl supports IMAP and IMAPS, so I want to > > know if I can use it to retrieve/remove emails from my Gmail account? > > Yes you can. > > Jay on

Re: QoS Level on MQTT

Totally agree, adding another option it may be not the correct way, given the huge amount of options that curl already have. I will look closer on that, before starting to write any code. Thanks for the suggestion Greetings El lun., 28 de jun. de 2021 9:25 p.m., Dan Fandrich via curl-library < cur

Re: QoS Level on MQTT

On Mon, Jun 28, 2021 at 08:29:33PM -0400, Gealber Morales via curl-library wrote: > My intention is to add this option, for the publishing, in a way like this: > > curl -d 95 -qos 2 mqtt://localhost:1883/curl/mqtt > > The new option would be -qos ,  in case of omission  zero would be the > defau

  1   2   3   4   5   6   7   8   9   10   >