Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
Help us out in the curl project
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_lists.haxx.se>
Date: Mon, 27 Jan 2025 13:16:16 +0100 (CET)
Hello friends.
This is the first in a new series of monthly emails about what YOU can do to
help out in the curl project. Things we would appreciate help and assistance
with at the moment.
For general tips on how to get started helping out, start at [4].
## zsh completion script [1]
This script should be fixed to instead use the source code as input instead of
the dynamic --help output. That would not only solve this problem that makes
it depend on the terminal width, but also make it work for cross-compiles etc.
Ideally, we should write some kind of template for this so that we can
generate completion scripts for multiple shells based on the same fundament.
## using --interface with link-local IPv6 URL [2]
When you give the `--interface` option telling curl to use a specific
interface for its outgoing traffic in combination with a IPv6 address in the
URL that uses a link-local scope, curl might pick the wrong address from the
named interface and the subsequent transfer fails.
Example command line:
curl --interface eth0 'http://[fe80:928d:xxff:fexx:xxxx]/'
The fact that the given IP address is link-scoped should probably be used as
input to somehow make curl make a better choice for this.
## test curl from git master in your project
We struggled with the fact that a lot of our code is only really and properly
tested once we ship a new release. It would be much better for everyone if we
discovered bugs and regressions earlier - maybe before we release them.
If you can help us test curl in your environment/product a few weeks *before*
the next pending release just to verify that everything looks great, it would
be much appreciated. Maybe use a daily build [3] ?
## test experimental features
Build curl with one or more of these features enabled, use them and make sure
that they work the way you want to work and how the documentation says they
work:
- SSL session import/export
- HTTPS RR
- ECH
File issues when you find something wrong!
## Links
[1] = https://github.com/curl/curl/issues/16072
[2] = https://github.com/curl/curl/issues/14782
[3] = https://curl.se/snapshots/
[4] = https://curl.se/docs/help-us.html
Date: Mon, 27 Jan 2025 13:16:16 +0100 (CET)
Hello friends.
This is the first in a new series of monthly emails about what YOU can do to
help out in the curl project. Things we would appreciate help and assistance
with at the moment.
For general tips on how to get started helping out, start at [4].
## zsh completion script [1]
This script should be fixed to instead use the source code as input instead of
the dynamic --help output. That would not only solve this problem that makes
it depend on the terminal width, but also make it work for cross-compiles etc.
Ideally, we should write some kind of template for this so that we can
generate completion scripts for multiple shells based on the same fundament.
## using --interface with link-local IPv6 URL [2]
When you give the `--interface` option telling curl to use a specific
interface for its outgoing traffic in combination with a IPv6 address in the
URL that uses a link-local scope, curl might pick the wrong address from the
named interface and the subsequent transfer fails.
Example command line:
curl --interface eth0 'http://[fe80:928d:xxff:fexx:xxxx]/'
The fact that the given IP address is link-scoped should probably be used as
input to somehow make curl make a better choice for this.
## test curl from git master in your project
We struggled with the fact that a lot of our code is only really and properly
tested once we ship a new release. It would be much better for everyone if we
discovered bugs and regressions earlier - maybe before we release them.
If you can help us test curl in your environment/product a few weeks *before*
the next pending release just to verify that everything looks great, it would
be much appreciated. Maybe use a daily build [3] ?
## test experimental features
Build curl with one or more of these features enabled, use them and make sure
that they work the way you want to work and how the documentation says they
work:
- SSL session import/export
- HTTPS RR
- ECH
File issues when you find something wrong!
## Links
[1] = https://github.com/curl/curl/issues/16072
[2] = https://github.com/curl/curl/issues/14782
[3] = https://curl.se/snapshots/
[4] = https://curl.se/docs/help-us.html
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2025-01-27