Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs/libcurl: add TLS backend info for all TLS options #13168

Closed
wants to merge 3 commits into from

Conversation

bagder
Copy link
Member

@bagder bagder commented Mar 21, 2024

All man pages that are listed to be for TLS now must also specify exactly what TLS backends the option works for, or use * if they all work.

cd2nroff makes sure this is done and that the listed backends(s) exist.

All man pages that are listed to be for TLS now must also specify
exactly what TLS backends the option works for, or use `*` if they all
work.

cd2nroff makes sure this is done and that the listed backends exist.

Closes #13168
@@ -10,6 +10,8 @@ See-also:
- curl_easy_setopt (3)
Protocol:
- TLS
TLS-backend:
- *
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it your intention for it to render as * because I think All would be easier to understand

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I primarily think of machine parsing this, but using All is indeed a good idea for the human readers.

@bagder
Copy link
Member Author

bagder commented Mar 22, 2024

Using this info, I'm working on generating a support matrix for the website. Here's a current screenshot of what we can now use this info for.
Screenshot 2024-03-22 at 09-33-03 TLS backend support of libcurl options

@bagder bagder closed this in c577500 Mar 22, 2024
@bagder bagder deleted the bagder/tls-backend branch March 22, 2024 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants