On Tue, May 28, 2024 at 05:52:08PM -0500, Bill Pierce via curl-library wrote:
> I like to figure things like this out myself. I find that it's the best way
> to learn how things work. So, I
> grabbed the sources from github using Git Bash on May 24, 2024, but when I
> tried to compile a test
On Sun, Mar 31, 2024 at 11:24:27AM +0200, Daniel Stenberg wrote:
> On Sat, 30 Mar 2024, Dan Fandrich via curl-library wrote:
>
> > SPDX seems to be the standard SBOM format for this that tools are
> > starting to expect. The format is able to handle complex situations,
>
On Sat, Mar 30, 2024 at 06:29:48PM +0100, Daniel Stenberg via curl-library
wrote:
> Any proposals for how to document the exact set of tools+versions I use for
> each release in case someone in the future wants to reproduce an ancient
> release tarball?
SPDX seems to be the standard SBOM format
On Tue, Mar 26, 2024 at 03:16:31PM -0600, R C via curl-library wrote:
> btw; you mentioned : "curl versions since 7.75.0 have AWS signature
> calculation
> built-in, with the
>
> --aws-sigv4 option."
>
> is there something similar, a function, in libcurl?
--libcurl tells me it's
On Tue, Mar 26, 2024 at 02:17:10PM -0600, R C via curl-library wrote:
> > > -H "Host: $URL" \
> > This is seldom needed because curl adds it on its own.
> without it the script doesn't work with minio
[...]
> > > ${PROTOCOL}://$URL${MINIO_PATH}
I don't know what minio is, but looking at
On Tue, Mar 26, 2024 at 11:36:07AM -0600, R C via curl-library wrote:
> I am trying to find out how to write something, using libcurl, to do some io
> with a minio object store (s3 compatible)
>
> I did go a bit through the examples page (some I have used as een example for
> other projects), but
Is the code calling curl_global_cleanup() before checking for leaks? Does this
happen on the latest curl releae (8.5.0)?
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
On Mon, Jan 29, 2024 at 08:59:03PM +, Stephen Booth via curl-library wrote:
> I eventually tracked the problem down to the bearer token being passed
> having an extra newline inserted at the end. This was copied through to
> the http request (adding a blank line and making the server ignore
On Mon, Jan 29, 2024 at 07:33:59PM +, Jeff Mears via curl-library wrote:
> I have code that’s attempting to use CURLFORM_STREAM with curl_formadd, and it
> is getting a CURLE_SEND_FAIL_REWIND error from the library.
>
> Looking at the libcurl code, it looks like it might be a bug, but it’s
On Wed, Jan 17, 2024 at 03:28:11PM +0100, Nejc Drašček via curl-library wrote:
> I'm using ftp library ( github.com/embeddedmz/ftpclient-cpp ), which under
> the hood uses libcurl, and some requests are "polluting" stdout with http
> headers:
>
> Last-Modified: Mon, 15 Jan 2024 14:32:44 GMT
>
On Thu, Jan 18, 2024 at 01:46:34PM +0300, Sergey Bronnikov via curl-library
wrote:
> Before Curl version 8.4.0 everything worked fine (exactly with Curl 8.3.0),
> but after updating Curl to 8.4.0 in our HTTP client
Have you tried 8.5.0? There have been some important HTTP/2 changes since that
On Wed, Jan 17, 2024 at 03:28:11PM +0100, Nejc Drašček via curl-library wrote:
> I'm using ftp library ( github.com/embeddedmz/ftpclient-cpp ), which under
> the hood uses libcurl, and some requests are "polluting" stdout with http
> headers:
>
> Last-Modified: Mon, 15 Jan 2024 14:32:44 GMT
>
On Thu, Jan 11, 2024 at 10:44:42AM -0300, Samuel Henrique via curl-library
wrote:
> I have recently pushed an experimental build of curl with parallel test
> execution on Debian. This was done with the hopes of helping reporting issues
> and understanding if it's feasible to enable it for
On Wed, Dec 13, 2023 at 09:49:07PM +, Dmitry Karpov via curl-library wrote:
> I propose to add a simple check for the cookie file name length and call
> fopen() only if it is greater than zero like:
Sounds reasonable.
>if(data) {
> FILE *fp = NULL;
> -if(file) {
> +if(file
On Thu, Dec 07, 2023 at 08:02:04PM +0100, Jeroen Ooms via curl-library wrote:
> I am looking for a way in libcurl to trigger a callback once, after a
> http request has been completely submitted (including upload if any),
> but before the server has responded. So basically when we have done
> our
On Fri, Nov 24, 2023 at 08:25:05PM +0100, Max Kellermann via curl-library wrote:
> For the long term, I was wondering whether libcurl would be interested
> in incorporating a systemd-resolved mode if I were to submit a pull
> request.
Wouldn't it work to simply switch to c-ares for resolving
On Wed, Nov 22, 2023 at 07:26:15PM +, Nimit Dhulekar via curl-library wrote:
> We have been using statvfs as a CURLOPT_QUOTE command via libcurl to identify
> whether the entry on the SFTP server is a file or folder. Is there any way to
> know in advance (preferably through libcurl) that a
On Thu, Oct 26, 2023 at 03:42:34PM +0200, Hugo Valtier via curl-library wrote:
> Instead of using the Path Gateway it uses the Trustless Gateway which
> answers with a stream of blocks and walks the merkle-tree, verifies
> hashes and deserializes it on the fly.
> This would make curl or libcurl
On Tue, Oct 17, 2023 at 12:29:55PM +, m brandenberg via curl-library wrote:
> On Mon, 16 Oct 2023, Matt Toschlog via curl-library wrote:
> > I'm using libcurl in a voice server app running on Ubuntu 20.04 on an
> > Amazon AWS EC2 instance. When I get around 500 users on the system I
> > start
On Fri, Oct 06, 2023 at 02:54:22PM +, Taw via curl-library wrote:
> Hi, I am trying to use libcurl to test a handshake with an internal server.
> Unfortunately GET/HEAD methods do no work, I get 404 error from the server.
> Practically I would like the cURL equivalent of this command: "openssl
On Tue, Sep 26, 2023 at 11:29:16PM +0200, Mac-Fly via curl-library wrote:
> To rant a little: I don't now whats wrong with the internet these days
> and why such checks are required at all. I am sure they break a lot of
> applications like mine! (Rant off.)
You're preaching to the choir here.
>
On Sat, Sep 23, 2023 at 08:16:42PM +0200, Christian Weisgerber via curl-library
wrote:
> So in the end this regress test is built on assumptions and is
> therefor non-portable and prone to fail.
That basically verifies my guess as to what was happening. Thanks for following
up on this.
Dan
On Thu, Sep 21, 2023 at 12:08:33PM -0400, Anass Meskini via curl-library wrote:
> Thanks Dan for the clarification.
> I think it might be worth mentioning in the doc that this function might
> create
> a thread.
It is called the "threaded resolver" after all, and that name is found in 8
On Wed, Sep 20, 2023 at 09:11:32PM -0400, Anass Meskini via curl-library wrote:
> I compiled curl from the github repository with --with-openssl then I compiled
> multi-app.c.
> When I run the program in gdb and add a breakpoint for pthread_create I see:
curl will use the threaded resolver option
On Tue, Sep 19, 2023 at 01:47:45PM +0200, Daniel Stenberg wrote:
> Maybe we should consider adding a way to
> disable/enable tests based on the OS name where it runs?
There's already the "win32" feature for that platform since it's needed often
because of its "special" behaviour. For
On Mon, Sep 18, 2023 at 01:13:34PM +0200, Christian Weisgerber via curl-library
wrote:
> Dan Fandrich:
> > I wanted to try this patch on NetBSD to see if it's related
> > to Nagle's algorithm, but couldn't get to the point where I could try it:
>
> > -http://%HOSTIP:%HTTPPORT/we/want/%TESTNUMBER
On Mon, Sep 18, 2023 at 09:26:36AM -0400, Anass Meskini via curl-library wrote:
> When I run my program in valgrind, I see memory errors. What am I doing wrong?
Both these instances occur in GnuTLS, which deliberately uses some undefined
memory in its operation. It has code to mark these areas as
On Sun, Sep 17, 2023 at 10:43:17PM +0200, Christian Weisgerber via curl-library
wrote:
> The comment for test1474 says "This test is quite timing dependent and
> tricky to set up." On OpenBSD, it fails every time for me. And this
> is not an overloaded machine.
I've noticed failures on the
On Fri, Sep 01, 2023 at 01:53:27PM -0400, rsbec...@nexbridge.com wrote:
> Slight change, please. The i386 should be x86 (and eventually x86_64 when I
> get the 64-bit builds working).
i386 is a historical tag that basically means 32-bit Intel x86 architecture
these days. We should probably
On Thu, Aug 31, 2023 at 01:50:07PM -0400, rsbec...@nexbridge.com wrote:
> On Thursday, August 31, 2023 1:41 PM, Dan Fandrich wrote:
> >On Thu, Aug 31, 2023 at 11:09:58AM -0400, Jeffrey Walton via curl-library
> wrote:
> >> I think you should change strategies. You should use sed to change
> >>
On Thu, Aug 31, 2023 at 11:09:58AM -0400, Jeffrey Walton via curl-library wrote:
> I think you should change strategies. You should use sed to change
> references from -lz to libz.a (and friends).
While that would work, devs shouldn't need to do this. curl's configure is
simply doing the wrong
On Wed, Aug 30, 2023 at 06:08:38PM -0400, rsbec...@nexbridge.com wrote:
> Unfortunately, the packaging team for the platform did not help on this one.
> zlib.h is in the /usr/coreutils/include directory, the zlib.a, zlib.so,
> zlib.so.1.2.11 are in /usr/coreutils/lib (which collide). The zlib.pc
On Wed, Aug 30, 2023 at 05:03:34PM -0400, rsbec...@nexbridge.com wrote:
> Actually, there is no libtool on the platform, so upgrading will be
> difficult. No LIB, INCLUDES, or other compile-related environment variables.
Then it will be using the built-in libtool, which should be fairly recent.
On Wed, Aug 30, 2023 at 03:27:34PM -0400, Randall via curl-library wrote:
> ln: failed to create hard link '.libs/libcurl.lax/lt1-libz.a' =>
> '/usr/coreutils/lib/libz.a': Cross-device link
This looks like a bad assumption on the part of libtool that a hard link is
possible. I don't know why it's
On Mon, Aug 28, 2023 at 08:11:14PM +0300, Florents Tselai via curl-library
wrote:
> Is there any documentation / how to on the process I’d need to follow to add a
> new option to the tool ?
> Particularly the sequence of files / function / macros I’d need to
There are lots of documentation in
On Tue, Aug 22, 2023 at 04:06:17PM +0200, Jimmy Sjölund via curl-library wrote:
> Considering that Cirrus CI lists curl and use the logo on their first page
I didn't notice that before! Usually, it's the companies that pay to show up
on the curl sponsors page. curl has become such a trusted
The curl Cirrus CI pages now link[1] to a notice that they're limiting their
free CI tier starting next week. The new limit will be "50 compute credits" per
month, which seems to buy us about 260 hours of compute time. Unfortunately,
curl has been using about 6000 hours of compute time per month
On Wed, Jul 19, 2023 at 12:30:02AM +0200, Patrick Monnerat via curl-library
wrote:
> No tests on OS400: would need perl among other features. These are available
> under PASE which is an AIX emulation, but certainly not native OS400.
If the tests won't even run there, then maybe you can convince
On Sat, Jul 08, 2023 at 08:18:26PM +, Ligya Fernandes via curl-library
wrote:
> Desde já agradeço a ajuda, Dan! Você sabe onde eu posso encontrar uma
> biblioteca libcurl que seja compatível? Pode me indicar o local, por meio de
> um
> link, se não for pedir muito?
My point is that you
On Fri, Jul 07, 2023 at 08:21:33PM +, Ligya Fernandes via curl-library
wrote:
> Fatal: failed to load library "libcurl -4.dll
This is an indication that your git installation is corrupt. Whatever way you
installed
git should have also installed a compatible libcurl library.
Dan
--
On Fri, Jun 09, 2023 at 10:35:45AM +0200, Daniel Stenberg via curl-library
wrote:
> The idea is simple: for every existing option we have to curl_easy_setopt(),
> there should be at least one full-size stand-alone example (in
> docs/examples/) showing how it could be used.
This would be really
On Thu, Jun 08, 2023 at 05:40:04PM +0200, Daniel Stenberg via curl-library
wrote:
> Just a few days ago, Dan Fandrich merged the necessary commits into master
> that now lets us try out running the curl tests in parallel as compared to
> the old serial way.
It's been a long road of refactoring
On Mon, May 29, 2023 at 11:41:04PM +0200, Przemysław Sobala via curl-library
wrote:
> If I understand the documentation correctly, the HSTS cache is applied to each
> curl easy handle and it's read and written on each easy handle open and close
> action.
> I'd like to use the in-memory cache as
On Thu, May 25, 2023 at 05:23:58PM +0200, Johny Bravo via curl-library wrote:
> I have tried websocket API, but I cannot get it working and receive message.
> If I use the ws in JavaScript, I have:
>
> var socket = new WebSocket( "wss://some_url", "example");
>
> However, I dont know, how to set
On Wed, May 17, 2023 at 09:48:39AM +0200, Rainer Jung via curl-library wrote:
> I just wanted to note, that the test suite now uses the perl module
> Memoize.pm. That module is contained in the perl base package eg. for RHEL
> 7, but for RHEL 8 must be installed as perl-Memoize.
I had assumed
On Wed, Apr 19, 2023 at 01:26:13PM +, Arnaud Compan via curl-library wrote:
> Is there a way to silence the internal progress meter ?
There's an opt for that: CURLOPT_NOPROGRESS
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:
On Wed, Apr 12, 2023 at 03:08:02PM -0700, David Castillo via curl-library wrote:
> What permissions does OpenSSL need to read the certificates?
I'm guessing the app would need the READ_EXTERNAL_STORAGE permission.
--
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:
On Fri, Mar 24, 2023 at 05:45:18PM +, Philippe Lefebvre via curl-library
wrote:
> we are having some crashes when using CURL library. We are in mutltithreaded
> environment, and in these crashes mostly happend on heavy/loaded process (lots
> of data, lots of Get/Post requests).
The first
On Thu, Mar 23, 2023 at 01:24:18PM -0400, Jeffrey Walton wrote:
> You can run particular self tests rather than the entire test suite.
The problem is, I'm changing the test suite itself so I need to run everything
to get a better chance of hitting the edge cases. Stefan is similarly working
on
On Thu, Mar 23, 2023 at 08:57:20AM +0100, Stefan Eissing wrote:
> very happy that you will work on this. I like to run the test suite locally
> before a large push and the time it takes on my machine is around 10 minutes.
> I'd very much appreciate that to go down!
I've been hit pretty hard
On Wed, Mar 22, 2023 at 04:10:32PM -0700, bch via curl-library wrote:
> This is a curl binary, or a release tarball
The daily tar balls are available at https://curl.se/snapshots/
> (how much processing *does* go on
> from a repo checkout -> curl-x.y.z.tar.gz?)?
I think it's just running
On the long road to 8.0.0, curl has taken on close to 1600 test cases
[1] that help verify that it stays running correctly. These tests are
one of the ways that curl stays operating reliably year after year, but
the downside is that they can take an annoyingly long time to run.
Normal test
On Wed, Mar 22, 2023 at 09:17:48AM +0100, Daniel Stenberg via curl-library
wrote:
> So, how about this for adjusted release cycle and release management:
>
> - Increase the post-release ("cool down") margin before we open the feature
>window. We currently have it 5 days, we could double it
On Tue, Mar 21, 2023 at 12:40:28PM -0400, Timothe Litt via curl-library wrote:
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
On Wed, Mar 22, 2023 at 12:10:56AM +0100, Daniel Stenberg wrote:
BTW, "regression" is just another word for "test coverage gap", since
if we had tested the thing we would've detected the problem and the
bug would not have been shipped. It is important that we learn from
the regressions and
I've been getting a feeling that there have been more curl functional
regressions (compared to plain bugs) in releases over the last few years. I
don't know if that's true or not, but the pace of bug fixes generally has been
going up (see https://curl.se/dashboard1.html#bugfix-frequency). I'm
On Thu, Mar 02, 2023 at 05:51:07PM +0100, Daniel Stenberg via curl-library
wrote:
> Today I fell into an issue with PR #10651 where everything builds fine,
> execpt on Windows with mingw v1.
>
> There's really nothing unusual with that while working on a PR, but this
> time it struck that I
On Tue, Feb 21, 2023 at 03:19:12AM +, Matthew Bobowski wrote:
> No cast is necessary.
>
> #define CURLAUTH_BEARER (((unsigned long)1)<<6)
Ah, good. Many of the other contants (like CURLSSH_AUTH_* and CURLFTPAUTH_*)
*do* need that cast.
--
Unsubscribe:
On Tue, Feb 21, 2023 at 03:01:53AM +, Matthew Bobowski via curl-library
wrote:
> c = curl_easy_setopt(pCurl, CURLOPT_HTTPAUTH, CURLAUTH_BEARER);
Don't forget to cast this to a long; this makes a difference in some
environments.
Dan
--
Unsubscribe:
On Thu, Feb 09, 2023 at 05:14:12PM +0100, Daniel Stenberg via curl-library
wrote:
> On Thu, 9 Feb 2023, Diogo Sant'Anna via curl-library wrote:
> > Checking https://curl.se/dev/release-procedure.html, it seems the
> > project's release is still managed manually. Have you considered
> > migrating
On Tue, Jan 31, 2023 at 09:58:13AM +0100, Frederik Seiffert wrote:
> Could you please explain what you mean by "compiling with a different
> resolver"? I didn’t see any build options like that. Do you maybe mean
> building with "CURL_DISABLE_SOCKETPAIR"?
I mean using the
Are you looking for CURLOPT_CONNECT_ONLY?
--
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
On Mon, Jan 16, 2023 at 04:30:48PM +0100, Frederik Seiffert via curl-library
wrote:
> When receiving CURL_POLL_REMOVE, I call dispatch_source_cancel() [2] to stop
> the dispatch source. As this is done asynchronously, it is required to wait
> for the cancellation handler before closing the
On Wed, Jan 11, 2023 at 02:24:57PM +0100, Daniel Stenberg via curl-library
wrote:
> Like this:
>
> $ curl -V
> WARNING: this libcurl is Debug-enabled, do not use in production
Writing the same thing as the first line of -v output would double the chance
it's actually seen.
--
Unsubscribe:
On Fri, Jan 06, 2023 at 01:44:48PM -0400, Calvin Buckley via curl-library wrote:
> - I have capacity on a shared system intended for open source
> development. I should be able to set up some kind of CI runner here.
> The very annoying part is Go isn't supported (bar an experimental
>
On Fri, Dec 30, 2022 at 05:24:46PM +, Samantray Bhuyan, Madhusudan (GE
Digital) via curl-library wrote:
> How to I redirect libcurl verbose output to a log file . I found https://
> stackoverflow.com/questions/38720602/
> getting-verbose-information-from-libcurl-to-a-file but the log file is
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 subtle but pretty useful for
avoiding spoofing. Based on the name registration policies
On Fri, Sep 30, 2022 at 09:43:39AM +0200, Daniel Stenberg via curl-library
wrote:
> libcurl hold credentials (passwords for servers and proxies) in memory in
> clear text, potentially for a long time. If something goes wrong and that
> memory is accessed by an external party, things would be bad.
On Tue, Nov 01, 2022 at 08:42:45PM +0800, frankfreak via curl-library wrote:
curl 7.70.0 (x86_64-pc-linux-gnu) libcurl/7.29.0 NSS/3.53.1 zlib/1.2.7 libidn/
1.28 libssh2/1.8.0
You're using mismatched versions—an over 2-year-old CLI (ver. 7.70.0) with an
almost 10-year-old library (ver.
On Wed, Oct 26, 2022 at 10:26:40AM -0400, Randall via curl-library wrote:
> If we build under 64-bit, which is scheduled later in the
> year, then there is no need to override the defaults. Do you want a PR for
> this?
Keep in mind that this will cause an ABI break on this platform.
--
On Mon, Oct 17, 2022 at 04:34:05PM +0200, Daniel Stenberg via curl-library
wrote:
> On Mon, 17 Oct 2022, Timothe Litt via curl-library wrote:
>
> > > My initial PR for this work: https://github.com/curl/curl/pull/9750
> > >
> > Why change the default behavior?
>
> For improved privacy. Because
On Thu, Oct 13, 2022 at 08:46:20AM +, Arnaud Compan via curl-library wrote:
> In details, I've added the function in lib/multi.c:
> void my_test(struct Curl_easy *data)
> {
> }
> And in include/curl/multi.h:
> CURL_EXTERN void my_test(CURL *curl_handle);
On Thu, Sep 29, 2022 at 09:58:58PM +, Mark Fanara wrote:
>> Some servers have an issue with 100-continue, and I don't recall which
>> version
>> of libcurl enabled it by default. You could try disabling it and see what
>> happens. It theoretically shouldn't have anything to do with MTU,
On Thu, Sep 29, 2022 at 08:05:00PM +, Mark Fanara wrote:
> Sorry if my response is not per best practices as far as formatting goes. I
> will respond to a number of your questions here rather than inline.
See https://curl.se/mail/etiquette.html#Do_Not_Top_Post
> As to MTU - I of course
On Thu, Sep 29, 2022 at 01:58:23PM +, Mark Fanara via curl-library wrote:
> Recently the device vendor updated the OS image to Debian Buster.
The subject of this message doesn't match this line. If it's an OS upgrade that
happened, then it's much more than just a newer libcurl that's
On Thu, Sep 22, 2022 at 11:48:58PM +, Dmitry Karpov via curl-library wrote:
> And for me the biggest problem is that I just can't change the code of
> certain curl-based components used in my application.
> They are written by some other developers and closed for any modifications.
That is
On Wed, Sep 21, 2022 at 06:21:08PM -0700, Dan Fandrich wrote:
> On Thu, Sep 22, 2022 at 12:24:57AM +, Dmitry Karpov via curl-library
> wrote:
> > > If Curl_ipv6works() were not called in the CURL_IPRESOLVE_V6 case, would
> > > that solve the issues that are remaining?
> >
> > Your question
On Thu, Sep 22, 2022 at 12:24:57AM +, Dmitry Karpov via curl-library wrote:
> > If Curl_ipv6works() were not called in the CURL_IPRESOLVE_V6 case, would
> > that solve the issues that are remaining?
>
> Your question was:
> "So, if libcurl eliminated that call in the CURL_IPRESOLVE_V4 case,
On Wed, Sep 21, 2022 at 10:46:45PM +, Dmitry Karpov via curl-library wrote:
> I think that my proposal will provide useful customization for dual-stack
> curl applications, and I am not sure that I fully understand your objections
> like " It might in your situation, but it wouldn't in
On Wed, Sep 21, 2022 at 08:19:46PM +, Dmitry Karpov via curl-library wrote:
> Daniel's PR fixed the issue only for CURL_IPRESOLVE_V4, but not for
> CURL_IPRESOLVE_WHATEVER and CURL_IPRESOLVE_IPV6.
> Even with his PR, both CURL_IPRESOLVE_WHATEVER and CURL_IPRESOLVE_IPV6 will
> use
On Wed, Sep 21, 2022 at 07:40:10PM +, Dmitry Karpov via curl-library wrote:
> Yes, doing things "lazily" in Daniel's PR fixes the problem for explicit
> CURL_IPRESOLVE_V4, which will not call Curl_ipv6works() anymore.
> But the problem is still there for the CURL_IPRESOLVE_WHATEVER, which is
On Wed, Sep 21, 2022 at 11:50:50AM -0700, Ben Greear via curl-library wrote:
My opinion is to stay conservative, for those wanting/required to build recent
curl on ancient
systems with old compilers...
This certainly makes life easier for people who are forced to use
ancient systems, but it
On Tue, Sep 20, 2022 at 07:24:42PM +, Dmitry Karpov wrote:
Not necessarily.
If we have a bunch of applications on the system with large codebases which use CURLOPT_IPRESOLVE = AUTO in too many places, then all these places should detect somehow that "IPv6 doesn't work" and change the resolve
On Tue, Sep 20, 2022 at 06:58:31PM +, Dmitry Karpov via curl-library wrote:
> To cover such a range of cases, curl application needs a more flexible
> approach for detection whether IPv6 works on the "system level".
> And I guess the "curl_global_init_ipv6() with callback" provides such
>
On Sat, Sep 10, 2022 at 01:44:42PM +0200, Patrick Monnerat via curl-library
wrote:
> - Drop support for non-64bit curl_off_t.
FWIW, https://wiki.debian.org/ArchitectureSpecificsMemo#Summary shows that all
Debian-supported architectures (and I count 30 of those) have a 64-bit
long long type.
On Wed, Sep 07, 2022 at 05:19:36PM -0400, Dennis Clarke via curl-library wrote:
> So I am guessing that there is a way for me to re-run test 831 in verbose
> detail.
The most straightforward for an in-tree build is:
cd tests
./runtests.pl -a -n -p -v -d 831 834 877 880 933 936 2023 2024 2026
On Wed, Sep 07, 2022 at 07:28:32PM -0400, Dennis Clarke via curl-library wrote:
The LD_PRELOAD borks things up badly :
s$
s$
LD_PRELOAD=/opt/bw/build/curl-7.85.0_sunos5.10_sparcv9_sslv3.003/tests/libtest/.libs/libhostname.so
/usr/xpg4/bin/sed -e 's/foo/bar/'
ld.so.1: sed: fatal:
On Tue, Sep 06, 2022 at 11:57:24PM -0400, Dennis Clarke via curl-library wrote:
TESTFAIL: These test cases failed: 831 834 877 880 933 936 2023 2024 2026
2027
So not sure how to proceed. In the past I was generally able to get a
fantastic clean results from curl.
So then ... how to proceed
On Fri, Jun 17, 2022 at 01:39:00PM +0200, Daniel Stenberg via curl-library
wrote:
> I would like to provide websockets data with the CURLOPT_WRITEFUNCTION
> callback as well. But how would libcurl provide the additional necessary
> metadata?
I'm admittedly not very familiar with websockets, but
On Mon, Jun 06, 2022 at 03:40:09PM -0700, Adam Light via curl-library wrote:
> However the problem is that it appears that when the url is set using
> CURLOPT_CURLU, curl_easy_getinfo for CURLINFO_EFFECTIVE_URL returns an empty
> string. So unless I am missing something it doesn't seem to be
On Wed, May 25, 2022 at 04:10:40AM +, 范 范珏 via curl-library wrote:
> I am working on http/https digest auth using libcurl,tried 7.48.0 and
> 7.64.1,neither of them can work.
Those versions are 6 years and 3 years old, respectively. Have you tried with
the latest version 7.83.1 to see if still
On Thu, May 19, 2022 at 02:24:15AM +0200, TheAssassin via curl-library wrote:
> On 18.05.22 22:57, Dan Fandrich via curl-library wrote:
> > This sounds like it would become a source of problems, since the same
> > application running on exactly the same OS would have diff
On Wed, May 18, 2022 at 08:05:41PM +0200, TheAssassin via curl-library wrote:
> The issue I am facing with this is that apparently, libcurl just hardcodes
> the path to the CA certificate bundle (e.g., the system-provided bundle).
> This behavior is problematic. An AppImage built on CentOS 7 using
On Wed, Apr 20, 2022 at 04:41:22PM +0200, Andreas Falkenhahn via curl-library
wrote:
> is there any convenient way of escaping a URL so that it can be passed to
> CURLOPT_URL?
The curl_url API can do this, specifically, the CURLU_URLENCODE option.
curl_url is the preferred means of parsing URLs
On Tue, Apr 12, 2022 at 07:07:51PM +0200, Julien Matthey via curl-library wrote:
> I get "curl_easy_perform() failed: Unsupported protocol" for https requests:
[...]
> And here is my problem with it: it works with the curl.exe executable I also
> built! Example:
>
> $curl *https*://www.google.com
On Sat, Mar 19, 2022 at 01:06:53PM +0530, Devang Modi via curl-library wrote:
> I m working on a project that is based upon PROGRESS/OpenEdge software.
> I am looking to integrate libCurl for this project but due to the native
> platform language support issue
> I am not able to use the following
On Mon, Feb 07, 2022 at 11:10:39PM +0100, Daniel Stenberg via curl-library
wrote:
> In order to get better overview and control of the jobs we run, I'm
> proposing that we create and maintain a single file that lists all the jobs
> we run. This "database" of jobs could then be used to run checks
On Thu, Feb 03, 2022 at 08:35:13PM -0500, Timothe Litt via curl-library wrote:
> 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).
> Set on-the-fly breakpoints
On Tue, Jan 25, 2022 at 07:31:31PM -0300, Rodrigo s via curl-library wrote:
> Well, the problem is that I can't install anything. Just run php... Is it
> possible?
A web search tells me that it's possible. See this link for example:
On Tue, Dec 14, 2021 at 01:29:11PM +0530, Ayesh Karunaratne via curl-library
wrote:
> With the addition of CURLOPT_PREREQFUNCTION, one could write a
> callback function to selectively block requests to certain IP/port
> ranges.
For the record, blocking requests by IP address has been possible
1 - 100 of 108 matches
Mail list logo
