Skip to content

tool_operate: reuse the schannel backend check - #15323

Closed
bagder wants to merge 1 commit into
masterfrom
bagder/transfer-schannel-check
Closed

tool_operate: reuse the schannel backend check#15323
bagder wants to merge 1 commit into
masterfrom
bagder/transfer-schannel-check

Conversation

@bagder

@bagder bagder commented Oct 17, 2024

Copy link
Copy Markdown
Member

The transfer_per_config is called once per new transfer. It now saves the result of the first TLS backend check done so that subsequent invokes are more efficient and reuses the existing knowledge.

@dfandrich

This comment was marked as outdated.

The transfer_per_config is called once per new transfer. It now saves
the result of the first TLS backend check done so that subsequent
invokes are more efficient and reuses the existing knowledge.

This change also splits the logic into several smaller functions.

Closes #15323
@bagder
bagder force-pushed the bagder/transfer-schannel-check branch from 56bb7bb to f1b553e Compare October 17, 2024 21:06
@bagder bagder closed this in 1b155f0 Oct 18, 2024
@bagder
bagder deleted the bagder/transfer-schannel-check branch October 18, 2024 06:14
pps83 pushed a commit to pps83/curl that referenced this pull request Apr 26, 2025
The transfer_per_config is called once per new transfer. It now saves
the result of the first TLS backend check done so that subsequent
invokes are more efficient and reuses the existing knowledge.

This change also splits the logic into several smaller functions.

Closes curl#15323
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