Skip to content

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

Closed
bagder wants to merge 3 commits into
masterfrom
bagder/tls-backend
Closed

bagder wants to merge 3 commits into
masterfrom
bagder/tls-backend

Conversation

@bagder

@bagder bagder commented Mar 21, 2024

Copy link
Copy Markdown
Member

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.

bagder added 2 commits March 21, 2024 22:38
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
@bagder
bagder force-pushed the bagder/tls-backend branch from 785b8ef to 6ccfde4 Compare March 21, 2024 22:47
Comment thread docs/libcurl/opts/CURLINFO_CAINFO.md Outdated
Protocol:
- TLS
TLS-backend:
- *

Copy link
Copy Markdown
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
Copy Markdown
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

bagder commented Mar 22, 2024

Copy link
Copy Markdown
Member Author

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

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.

2 participants