Re: Weird behavior when using DoH with the multi interface

This would seem to still leave the doh connections consuming data connections' cache quota. That is, doh can crowd out data connections, or at least makes the connection limit hard to explain or manage. The application has no control over how many DNS transactions it takes to resolve, e.g.

Re: Separate install

On 21-Dec-23 05:25, Daniel Stenberg via curl-library wrote: FYI A comment problem people seem to have, is installing a custom libcurl somewhere, only to find that their new curl executable does not use the new libcurl but instead load another/system libcurl. To help us not having to repeat

Re: Question/proposal about function returning pollfds from multi handle

On 18-Dec-23 10:40, Daniel Stenberg via curl-library wrote: On Thu, 14 Dec 2023, Dmitry Karpov via curl-library wrote: Probably, it would make sense to also return the count of descriptors, like: CURLMcode curl_multi_pollfds(struct curl_waitfd *ufds, unsigned int size, unsigned int*

Re: Large download speed deviations for CURLOPT_MAX_RECV_SPEED_LARGE in 8.4.0

On 01-Dec-23 02:32, Dmitry Karpov via curl-library wrote: In my tests, I downloaded a 5 MB file from some local network server using different network speeds. The test client was running on Windows (mentioning it, just in case). Random thought.  Symptoms sound like different buffering.  5MB

Re: Strange connection persistence problem

You really need to provide a reproducer - as simple as possible. That said: is _URL a #define constant or a variable?  Your printf doesn't have a \n - if you're seeing one, perhaps _URL has a \n - which can confuse things when it's inserted into the headers (makes the headers end early).  I

Re: Adding Mozzila CA certificates

On 27-Nov-23 10:03, Luis Carlos Chalaca Figueira via curl-library wrote: Hello, While developing a crawler I realized that some websites that can be displayed by Chrome and Firefox would throw SSL errors on libcurl requests Exs: SSL connect error SSL routines::unsafe legacy renegotiation

Re: Add CURLOPT_SERVER_RESPONSE_TIMEOUT_MS option

On 20-Nov-23 08:32, Cristian Rodríguez via curl-library wrote: On Sun, Nov 19, 2023 at 5:08 PM Ray Satiro via curl-library wrote: On 11/19/2023 2:35 PM, Timothe Litt via curl-library wrote: > > While I agree that a struct timespec* would be a better choice, > co

Re: Add CURLOPT_SERVER_RESPONSE_TIMEOUT_MS option

On 19-Nov-23 15:07, Ray Satiro via curl-library wrote: On 11/19/2023 2:35 PM, Timothe Litt via curl-library wrote: While I agree that a struct timespec* would be a better choice, consistency in an API is important. All the other _MS functions could also use a stuct timespec (you get

Re: Add CURLOPT_SERVER_RESPONSE_TIMEOUT_MS option

On 19-Nov-23 13:01, Cristian Rodríguez via curl-library wrote: On Sat, Nov 18, 2023 at 11:05 AM Daniel Stenberg via curl-library wrote: On Sat, 18 Nov 2023, Yifei Kong via curl-library wrote: > However, there is only `CURLOPT_SERVER_RESPONSE_TIMEOUT` and no >

Re: Wrapper function for curl_easy_setopt()

On 24-Oct-23 06:24, Vladimir Levijev via curl-library wrote: Hi, We use curl library and a lot of curl_easy_setopt() calls in our application. When our application is run with curl library compiled without some features we can get the following error message from failed curl_easy_setopt()

Re: Proposal: URL API extension, second setter function to allow setting from CURLU object

On 23-Oct-23 08:28, Mark Gaiser via curl-library wrote: On Mon, Oct 23, 2023 at 8:57 AM Daniel Stenberg wrote: On Sun, 22 Oct 2023, Mark Gaiser via curl-library wrote: > I get that this is c-code and just the c-way of doing things. Still, it can > be simplified a lot, even in

Re: Getting a list of easy handles in a multi handle - possible?

On 26-Aug-23 15:12, Daniel Stenberg wrote: On Sat, 26 Aug 2023, Timothe Litt via curl-library wrote: Not very efficient if there are lots of handles.  You will scan the list O(n^2) looking for prev each time - or, I suppose create a hash. Between each invoke there may be N new handles added

Re: Getting a list of easy handles in a multi handle - possible?

On 26-Aug-23 15:05, Daniel Stenberg via curl-library wrote: On Sat, 26 Aug 2023, Jeroen Ooms wrote: I am also (still) interested: https://curl.se/mail/lib-2016-06/0002.html Seven years later, what do you know! At least I was positive about it already back then. How about something basic

Re: Getting a list of easy handles in a multi handle - possible?

On 26-Aug-23 14:27, Daniel Stenberg via curl-library wrote: On Sat, 26 Aug 2023, Richard W.M. Jones via curl-library wrote: It seems like the multi "knows" what easy handles it contains already (multi->easyp), so we shouldn't have to maintain this list ourselves. However I couldn't see

Re: Cirrus CI limiting free compute time

At $3500/mo, you could buy a pretty decent physical server in less than a month.  Last one I bought was ~USD $2500 - I went for a model year behind (besides being cheaper, I have no use for the "efficiency"/large core mixes).  Several Tb of disk, ECC memory, 6 cores (12 counting HT), 3.4GHz,

Re: NSS and gskit are getting the axe

With respect to CI: While I know little about OS400, Perldoc says that you *can *natively compile Perl with IBM's Visual Age compiler.   Most CPAN modules are either pure Perl, portable XS (a bunch of C macros), or provide a pure Perl alternative.  Whether the tests depend on any exceptions

Re: CURLUPART_PATH not inserting leading slash

On 08-Jun-23 03:18, Daniel Stenberg via curl-library wrote: On Thu, 8 Jun 2023, Pedro Henrique via curl-library wrote: but the code below results in 400 Bad Request due to the lack of the forward slash. So is it a bug or not? I can confirm that this is a bug and that it still exists in

Re: all previous curl CVEs as JSON ?

On 01-May-23 15:18, Daniel Stenberg wrote: * Rather than hiding in description, add key for "known exploits" -   value can be boolean. [will this be updated if updates are   discovered after publication?  If not, what's the value of having it?] We basically never get that information. I don't

Re: all previous curl CVEs as JSON ?

On 01-May-23 06:16, Daniel Stenberg via curl-library wrote: See https://github.com/curl/curl-www/pull/237 Let me know how we can perfect this. This JSON file will be automatically generated and provided on the curl site at a fixed URL. Good start.  A few things to consider: * Use

Re: The application does not have to keep the string around after setting this option

On 20-Apr-23 07:01, Andreas Falkenhahn via curl-library wrote: On 20.04.2023 at 12:31 Timothe Litt via curl-library wrote: If there are any cases where the string is not copied and must be retained, the documentation should say so explicitly. +1 To make matters more confusing, I've also

Re: The application does not have to keep the string around after setting this option

On 20-Apr-23 05:24, Frank Gevaerts via curl-library wrote: On Wed, Apr 19, 2023 at 06:47:42PM +0200, Andreas Falkenhahn via curl-library wrote: Many manpages of curl options that take a string say: "The application does not have to keep the string around after setting this option". Does this

Re: Recommended way of using a custom build of libcurl in a Node.js addon

m trying to solve and find out which one is the most reasonable to use here. On Tue, Mar 21, 2023 at 5:18 PM Timothe Litt via curl-library wrote: On 21-Mar-23 04:34, Darshan Sen via curl-library wrote: Hi! I'd like to incorporate a custom build of libcurl (with

Re: On more stable curl releases

I agree with the problem statement.  But there's no easy answer. I expect that with frequent patch releases, curl would end up in the situation of most M$ releases whose strategy is- "wait for the other people to find the bugs and only take the nth patch release."  And with fewer users, the

Re: Recommended way of using a custom build of libcurl in a Node.js addon

source and my users lack the technical skills required to build curl from source. That's why, I created this thread to learn about solutions for this problem that I'm trying to solve and find out which one is the most reasonable to use here. On Tue, Mar 21, 2023 at 5:18 PM Timothe Litt via

Re: Recommended way of using a custom build of libcurl in a Node.js addon

On 21-Mar-23 04:34, Darshan Sen via curl-library wrote: Hi! I'd like to incorporate a custom build of libcurl (with HTTP3 support) into a Node.js C++ addon that is going to be shipped to some systems that don't have curl or its dependencies installed.

Re: WebSocket feature request: is it possible to call write function when full frame is loaded only?

On 03-Feb-23 03:27, Daniel Stenberg via curl-library wrote: On Fri, 3 Feb 2023, Vitalii B. Avramenko via curl-library wrote:  Such partial data may be OK for HTTP protocol when we know for sure that we have "request/response" pattern and we can detect the end of data by HTTP protocol itself,

Re: Accidental debug-enabled version

Another option would be that building with  debug creates curl-debug and libcurl-debug (rather than curl and libcurl), which makes it really difficult to unknowingly make this mistake. It also handles libcurl-debug escaping into the wild and being silently loaded by applications.  And in a

Re: HTTP/3 options

On 04-Jan-23 03:08, Daniel Stenberg wrote: On Tue, 3 Jan 2023, Timothe Litt via curl-library wrote: Thanks, this is certainly an interesting idea. --http=3 - use http3, fall back to 2, 1.1, 1.0, 0.9, ... We don't use '='-separators in our option parser so unless we introduce it now

Re: HTTP/3 options

On 03-Jan-23 11:24, Daniel Stenberg via curl-library wrote: Hi team, I started to write down some ideas for two options to ask for HTTP/3 to be used by curl when we remove the experimental label for it. Hopefully during his coming spring. My notes exist only as a GitHub gist for now:

Re: option to disallow IDN ?

On 16-Dec-22 14:19, Dan Fandrich via curl-library wrote: On Fri, Dec 16, 2022 at 01:18:12PM -0500, Timothe Litt via curl-library wrote: And/or the callback registration could specify "all domain names", "Just IDN" - The browsers (at least Firefox) do something subt

Re: option to disallow IDN ?

On 15-Dec-22 03:06, Daniel Stenberg via curl-library wrote: Hello, After my recent blog post "IDN is crazy" [1], a few people have requested a new option to curl that prevents it from accepting/using IDN. To reduce the risk of getting exploited by one of the many trickeries you can do with

Re: Curl handle as a FILE *

On 06-Dec-22 11:42, Patrick Monnerat via curl-library wrote: On 12/6/22 15:50, Timothe Litt via curl-library wrote: On 06-Dec-22 09:24, Patrick Monnerat via curl-library wrote: It's a good idea. Thanks! I don't think your seek() semantics are correct. seek(SEEK_END) terminates

Re: Curl handle as a FILE *

On 06-Dec-22 09:24, Patrick Monnerat via curl-library wrote: On 12/6/22 13:08, Daniel Stenberg wrote: On Tue, 6 Dec 2022, Patrick Monnerat via curl-library wrote: Please find the source code and use examples of functions curl_fopen() and curl_fdopen() in attachement. These allow

Re: How to check if machine has network connectivity using libcurl api reliably?

On 22-Nov-22 04:23, Daniel Stenberg via curl-library wrote: On Tue, 22 Nov 2022, Dipak B via curl-library wrote: How can an Windows application integrated with libcurl find out reliably and quickly if the machine has any kind of network connectivity? Further there can be situations were Wifi

Re: How to check if machine has network connectivity using libcurl api reliably?

On 22-Nov-22 04:23, Daniel Stenberg via curl-library wrote: On Tue, 22 Nov 2022, Dipak B via curl-library wrote: How can an Windows application integrated with libcurl find out reliably and quickly if the machine has any kind of network connectivity? Further there can be situations were Wifi

Re: noproxy breakage

On 27-Oct-22 17:42, Randall via curl-library wrote: On October 27, 2022 5:30 PM, Daniel wrote: A regression in the noproxy filter functionality in 7.86.0 has been suggested to be reason enough for a patch release: https://github.com/curl/curl/issues/9813 We don't yet have any stated

Re: A more basic README.md ?

Agree, but you might want to keep the build status badges... Timothe Litt ACM Distinguished Engineer -- This communication may not represent the ACM or my employer's views, if any, on the matters discussed. On 23-Oct-22 06:15, Daniel Stenberg via curl-library wrote:

Re: [EXTERNAL] Re: On CURLOPT_AUTOREFERER privacy

On 17-Oct-22 16:57, Daniel Stenberg via curl-library wrote: On Mon, 17 Oct 2022, Dmitry Karpov via curl-library wrote: I'm all for adding an option to add the host-only behaviour as an option, but not to make it the default. Yes, I also think that this is the right way to do it. I hear

Re: On CURLOPT_AUTOREFERER privacy

On 17-Oct-22 09:46, Daniel Stenberg via curl-library wrote: Hello, When setting the CURLOPT_AUTOREFERER option, libcurl automatically sets the referer: header in following request (like when following redirects) to the URL of the previous transfer. This can be considered a minor privacy

Re: functypes: recv/send argument definitions

On 26-Sep-22 11:14, Daniel Stenberg via curl-library wrote: Hello! In my new PR[*], I am ripping out the old checks from configure and cmake that try to figure out what argument and return types recv and send want. The new system instead a) defaults to POSIX and b) offers functypes.h that

Re: Test 1452 failing on ElectroBSD when executed with valgrind

take over. Good hunting. Timothe Litt ACM Distinguished Engineer -- This communication may not represent the ACM or my employer's views, if any, on the matters discussed. On 25-Sep-22 10:11, Fabian Keil via curl-library wrote: Timothe Litt via curl-library wrote on 2022-09

Re: Test 1452 failing on ElectroBSD when executed with valgrind

The 56 exit code is the "Recv failure: Connection reset by peer" from curl. valgrind might affect timing. If you expect anyone to look into this, you probably should post the valgrind log (log/valgrind1452) to see what it is doing, and log/telnet_server.log to see why the telnet server is

Re: [EXTERNAL] Re: Feature request: provide ability to set a global callback function telling libcurl if IPv6 works on the system

This discussion revolves around some platforms on which it is difficult to efficiently determine if IPv6 is *not* available. Observations: * The proposed solutions involve determining the converse. * On a given platform, answer is likely to be stable for a very long time.  E.g. until a

Re: Above and beyond 32 protocols

On 10-Sep-22 07:44, Patrick Monnerat via curl-library wrote: On 9/13/21 13:01, Daniel Stenberg via curl-library wrote: Hi team. We added support for GOPHERS in late 2020. There's a new PR proposing support for the ManageSieve protocol. We had a PR previously suggesting Gemini support and

Re: git clone with basic auth in url directly returns authentication failure after 401 received under some git versions (fwd)

On 20-Aug-22 18:49, Daniel Stenberg via curl-library wrote: > FYI, > > Here's an interesting side-effect that the git team ran into as a > direct result of our fixing of CVE-2022-27774.  > > I responded on the git list: > https://marc.info/?l=git=166103499714595=2 I'm not convinced of the premise

Re: [Discussion] Have curl honor OpenSSH configurations

On 11-Aug-22 10:23, Randall via curl-library wrote: Washttps://github.com/curl/curl/issues/9285 Originally opened by Ben Voris. The request was to have curl support OpenSSH config specifications. I am opening a discussion on this subject from the above case. The ask is whether it would make

Re: IPv6 resolution problems for IPv4 resolve mode

The terminology and behaviors here are conflating two very different things: - What address types are added to the cache - What addresses are used for a connection. The name IPRESOLVE_* implies that it controls resolution, but the description says it controls "what kind of IP addresses to use

Re: Force content decoding

r decoding that would be used if the server would reply with the correct Content-Encoding vs implementing it in my WRITEFUNCTION. Best, Wolf On 7. Jul 2022, at 11:15, Timothe Litt via curl-library wrote: On 07-Jul-22 03:56, Wolf Vollprecht via curl-library wrote: Hi all, I have some data

Re: Force content decoding

On 07-Jul-22 03:56, Wolf Vollprecht via curl-library wrote: Hi all, I have some data that I am downloading where I know that it is gzip-encoded. However, the server does not respond with the correct header (and I don’t have control over it). I was wondering if there is a way to either

Re: About a websockets write callback

On 17-Jun-22 09:12, Weston Schmidt via curl-library wrote: I tend to agree that the existing function signature is a bit too restrictive. If you don't want a unique to WS function, how about adding a different variant across the board for folks? What about adding a CURLOPT_CTX_WRITEFUNCTION

Re: Deprecating 4 "wrong" RTMP protocol bits

I like a comma separated string: "https,imaps" is even easier to type than CURLPROTO_HTTPS|CURLPROTO_IMAPS You'd also need to do the same for CURLINFO_PROTOCOL (get the protocol used). BTW: Doc error: https://curl.se/libcurl/c/CURLINFO_PROTOCOL.html says "to receive the version"; I think

Re: How to handle CA certificate bundles in portable application bundles (e.g., AppImages)?

On 20-May-22 02:59, Daniel Stenberg wrote: On Thu, 19 May 2022, Timothe Litt via curl-library wrote: It would be nice to have a curl_easy_getinfo() along the lines of: |curl_easy_getinfo(CURL *curl, CURLINFO CURLINFO_CAINFO, char **path)| to get a string with the current bundle path

Re: IPv6 resolution problems for IPv4 resolve mode

On 23-May-22 07:21, Daniel Stenberg via curl-library wrote: On Fri, 20 May 2022, Dmitry Karpov wrote: I understand the rationale for keeping DNS entry in the cache for both addresses, but in my proposal, I suggest to use "dual-stack" DNS queries only for dual-stack and IPv6-only modes. This

Re: How to handle CA certificate bundles in portable application bundles (e.g., AppImages)?

On 19-May-22 04:38, Daniel Stenberg via curl-library wrote: On Wed, 18 May 2022, TheAssassin via curl-library wrote: I could imagine that (maybe in addition) to that search path, libcurl could allow developers to specify a list of bundles. I don't see how it makes any functional difference

Re: Funds, server hosting and more

On 18-May-22 07:08, Daniel Stenberg via curl-library wrote: On Wed, 18 May 2022, Ray Satiro via curl-library wrote: I suggest figure out and then document what the actual expenses are and charge for that rather than an arbitrary amount. I'd guess donors won't like arbitrary amounts as they're

Re: Problem using authentication in a request

Perhaps the device isn't using Basic authentication.  Or it requires TLS with basic. If you enable authentication on the device, and omit the --user to cURL, you should get a 401 from the device. What does the WWW-Authenticate header in that response show?  It will include one or more

Re: Libcurl curl_slist_append() leads to memory leak.

Besides not calling curl_slist_free_all() per list_append.html The list should be freed again (after usage) withcurl_slist_free_all . (Someone beat me to pointing that out...) If the code shown is complete, you're not using the headers

Re: Feature request about curlinfo option returning resolver status/error code

No.  No need to invent abstract codes.  Use the DNS RCODE + (if available) the ENS EDNS0 EDE (RFC8914). Optionally returning some resolver-specific data is fine, but neither a new set of abstract codes nor whatever a resolver produces should be primary. Something like |struct {| |   

Re: [PATCH v4] setopt: make curl_easy_vsetopt public

On 29-Mar-22 03:39, Drew DeVault via curl-library wrote: On Tue Mar 29, 2022 at 9:32 AM CEST, Daniel Stenberg wrote: I'm sorry, but whose job would you say it is to forward outputs from GitHub CI jobs from your patch to the mailing list because you won't go there and check yourself? I would

Re: An API for extracing (HTTP) headers?

On 22-Mar-22 07:00, Daniel Stenberg wrote: On Tue, 22 Mar 2022, Timothe Litt via curl-library wrote: curl_easy_header: did you consider returning an array of structures, rather than just one? I did. I decided that it wouldn't improve the API but would make memory management somewhat more

Re: An API for extracing (HTTP) headers?

On 22-Mar-22 04:01, Daniel Stenberg via curl-library wrote: On Tue, 15 Mar 2022, Daniel Stenberg via curl-library wrote: - https://github.com/curl/curl/pull/8593 I merged the headers API as experimental. On the blog: https://daniel.haxx.se/blog/2022/03/22/a-headers-api-for-libcurl/

Re: a strlen update

free() seems odd.  Since they vastly outnumber (malloc+calloc+realloc), likely many (most?) are free(NULL) -- e.g. clean up paths where something might have been allocated. If this is the case, they're relatively cheap - the call overhead + an early check for NULL arg. The 1 byte memcpy is

Re: A CI job inventory

On 08-Feb-22 02:39, Daniel Stenberg wrote: On Mon, 7 Feb 2022, Timothe Litt via curl-library wrote: Perhaps rather than add metadata, have a utility that each CI job runs to update a database at setup and/or exit. That would be super cool. It makes me curious if there isn't something like

Re: A CI job inventory

On 07-Feb-22 18:29, Daniel Stenberg wrote: On Mon, 7 Feb 2022, Timothe Litt via curl-library wrote: I see backends, but where are the protocols?  E.g. does a job test http(s)?  FTP?  etc. It seems sensible to generate a list of the supported protocol each CI builds, yes. To help generate

Re: A CI job inventory

Agree with the thrust of these comments. Perhaps rather than add metadata, have a utility that each CI job runs to update a database at setup and/or exit. This would also automate updating descriptions, etc as well as entering new jobs without a separate process. It could give you actual

Re: A CI job inventory

Oh, and there might be benefit in having a real database, or a script to load this file into one. You really don't want to create custom query/management code when SQL utilities abound. Timothe Litt ACM Distinguished Engineer -- This communication may not represent

Re: A CI job inventory

Should probably support multi-line values - e.g. description. I see backends, but where are the protocols?  E.g. does a job test http(s)?  FTP?  etc. Consider how to measure effectiveness - 100 seems like a lot. coverage?  How many bugs found?  Recently? May be worth running most effective

Re: Fewer mallocs is better, episode #47

On 03-Feb-22 21:02, Henrik Holst via curl-library wrote: problems is that ltrace produces zero output, if I compile curl with --no-pie then ltrace produces some output but not a single strlen for some reason so I gave up on that and found uftrace instead which works but only shows which

Re: Fewer mallocs is better, episode #47

On 03-Feb-22 20:09, Henrik Holst via curl-library wrote: the traces only shows that strlen was called, not on which string it was called so the digging is a bit time consuming). Doesn't have to be too painful; automate: Set on-the-fly breakpoints where strlen is called, and display the

Re: Fewer mallocs is better, episode #47

On 01-Feb-22 15:38, Thomas Dineen via curl-library wrote: Gentle People:     I know that this is a bit off from the current thread but consider this: "Few mallocs is good" Why?    One issue is that in many (all) Operating Systems malloc is a system call, where a system call causes one or

Re: Fewer mallocs is better, episode #47

On 27-Jan-22 06:25, Gavin Henry wrote: Perhaps the win was from reducing strlen() calls? They are often overused, and while they can be optimized to some extent, they are inherently slow at runtime. Unless a compiler is smart enough to detect a string constant, where x is a constant

Re: Fewer mallocs is better, episode #47

On 27-Jan-22 07:47, James Read via curl-library wrote: On Thu, Jan 27, 2022 at 12:06 PM Henrik Holst wrote: I wonder if the results that you see from that example is due to the short life of each connection, aka most of the time there is spent on the tcp-handshake (and

Re: Fewer mallocs is better, episode #47

ded before assuming they are present. Timothe Litt ACM Distinguished Engineer -- This communication may not represent the ACM or my employer's views, if any, on the matters discussed. /HH Den tors 27 jan. 2022 kl 11:52 skrev Timothe Litt via curl-library : On 27-Ja

Re: Fewer mallocs is better, episode #47

On 27-Jan-22 04:27, Daniel Stenberg via curl-library wrote: On Thu, 27 Jan 2022, Gavin Henry wrote: I remember in the OpenLDAP project when they removed/reduced the amount of times sizeofs that were used for performance gains. When is sizeof ever a slow operation? As we're only using C89,

Re: [EXTERNAL] Re:Re: [HELP] What's the underlying connection reusing policy, can it be RR

On 23-Jan-22 05:46, Daniel Stenberg via curl-library wrote: On Sun, 23 Jan 2022, 白水月 wrote: What I was doing is to send keepalive requests to the server. I'm just wondering if there is a more graceful solution. TCP keepalive is rarely enough to maintain a connection. It usually also

Re: CURLOPT_WRITEFUNCTION issues - warning: curl_easy_setopt expects a curl_write_callback argument

This is wandering off topic for curl. json_loadb wants the full JSON string. You can use the example previously cited, and call json_loadb where the transfer is complete.  Something like. https://curl.se/libcurl/c/getinmemory.html *else* { //* * Now, our chunk.memory points to a

Re: CURLOPT_WRITEFUNCTION issues - warning: curl_easy_setopt expects a curl_write_callback argument

I'm confused about what you're trying to do. outstream is an input parameter.  It will contain whatever you set in the CURLOPT_WRITEDATA option. If it's a json structure that's input to your callback, overwriting the pointer with json_loadb doesn't make sense. In fact, the value of

Re: CURLOPT_WRITEFUNCTION issues - warning: curl_easy_setopt expects a curl_write_callback argument

t; is fine. Timothe Litt ACM Distinguished Engineer -- This communication may not represent the ACM or my employer's views, if any, on the matters discussed. On 21-Jan-22 07:17, Gavin Henry via curl-library wrote: On Fri, 21 Jan 2022 at 11:36, Timothe Litt via curl-library wrote

Re: CURLOPT_WRITEFUNCTION issues - warning: curl_easy_setopt expects a curl_write_callback argument

Casting isn't the answer.  Read the error carefully.  You're returning a size_t (integer) from a function declared to return a function pointer.  The pointer is supposed to be to a function that returns a size_t. multiplying 2 size_t variables results in a size_t, not a function pointer.

Re: CURLOPT_WRITEFUNCTION issues - warning: curl_easy_setopt expects a curl_write_callback argument

It enables link-time optimizations.  The compiler/linker can see further into to the source, and detect errors not seen at the module level. It's saying that your callback routine must be declared/typedefed as a "curl_write_callback". Timothe Litt ACM Distinguished Engineer

Re: Question about DNS timeout in libCurl

with name servers, especially in dual-stack area. Thanks, Dmitry Karpov *From:* curl-library *On Behalf Of *Timothe Litt via curl-library *Sent:* Thursday, December 16, 2021 12:30 PM *To:* curl-library@lists.haxx.se *Cc:* Timothe Litt *Subject:* Re: Question about DNS timeout in libCurl On 1

Re: Question about DNS timeout in libCurl

On 16-Dec-21 15:07, Dmitry Karpov via curl-library wrote: How do other common getaddrinfo implementations handle (timeouts for) non-responding name reservers? It seems like behavior we should be able to mimick. The regular getaddrinfo() on Linux systems follows the resolv.conf spec and uses

Re: Mailing list (RFC2369) headers

On 25-Nov-21 08:39, Daniel Stenberg via curl-library wrote: On Thu, 25 Nov 2021, Daniel Stenberg via curl-library wrote: You may also wish to provide a redirect from the pipermail URL to the current archive since all archived/saved mail to the list contains the erroneous (old) URL for the

Re: Happy Eyeballs doesn't seem to work with c-ares when IPv6 name servers on top of the name server list don't respond

On 25-Nov-21 03:01, Daniel Stenberg via curl-library wrote: On Thu, 25 Nov 2021, Dmitry Karpov via curl-library wrote: It seems the problem is that even though libcurl implements Happy Eyeballs for DNS queries and runs A and queries in parallel, c-ares still goes through the list of name

Mailing list (RFC2369) headers

The (RFC2369) e-mail headers for this mailing list (curl-library) include: List-Archive: This URL format is standard for MailMan V2 mailing lists, but results in a 404 for this one. It appears that the value of List-Archive should be

Re: Custom resolve of Address

On 22-Nov-21 16:06, Marcel Hellwig via curl-library wrote: On 22.11.21 21:33, Timothe Litt via curl-library wrote: Why not just put the entries you need into hosts.txt ( Actually /etc/hosts or \Windows\System32\drivers\etc\hosts, or equivalent)? Because I don't know the host names

Re: Custom resolve of Address

Why not just put the entries you need into hosts.txt ( Actually /etc/hosts or \Windows\System32\drivers\etc\hosts, or equivalent)? Even embedded OSs support this, and the convention is to look there before consulting DNS.  This happens behind the system calls that do name resolution, so it's

Re: Name resolution timeout not respected, Curl_resolver_kill() hangs.

On 16-Nov-21 17:24, Daniel Stenberg via curl-library wrote: On Tue, 16 Nov 2021, Woody wrote: In case of error, couldn't we somehow "detach" the thread instead of skipping the join()? Would it not be cleaner? I suppose this is where my inexperience with thread programming shines through,

Re: How to build libcurl with OpenSSL without installing the latter?

--with-xxx can be confusing at first. The --with-openssl= doesn't point to the the openssl library, but to the directory above it. E.g. --with-openssl=/othersys means that openssl is found in: /othersys/include/openssl /othersys/lib/openssl /othersys/share/openssl The headers will be in

Re: Above and beyond 32 protocols

On 13-Sep-21 07:01, Daniel Stenberg via curl-library wrote: > > # Feedback > > I'm all ears. Especially if you have alternative solutions to suggest > or if you have an opinion on which way to go. > > This is not a problem we must solve *right now*, but I would feel > better if we have an idea

Re: Version 8 at 25 years

On 02-Sep-21 07:22, Daniel Stenberg via curl-library wrote: > > 2. We call that release 8.0.0 > > ... completely independently of what version we released immediately > before then and disregarding what we add or not in that release. We've > been ever-incresing the minor version number since the

Re: Hint: curl timeout simulation

For some reason, mail intended for Libcurl-development is being addressed to curl library. Note the discrepancy between the display name and address below. Since it's in the reply-address, I suspect a Mailman misconfiguration... Subject:Re: Hint: curl timeout simulation Date: Wed, 1