Thanks! Here are some good next steps:

1. Update docs/libcurl/symbols-in-version
2. Provide at least one test case that shows the feature working
3. Add documentation so that we can verify that the code seems to work as documented and vice versa

Analysis of PR #17246 at 3db12794:

Test 1119 failed, which has NOT been flaky recently, so there could be a real issue in this PR. Note that this test has failed in 540 different CI jobs (the link just goes to one of them).

Test 284 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Test 2301 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Test 2302 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Test 2101 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Test 987 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

Test 988 failed, which has NOT been flaky recently, so there could be a real issue in this PR.

There are more failures, but that's enough from Gha.

Generated by Testclutch

Thanks! Here are some good next steps:

1. Update docs/libcurl/symbols-in-version
2. Provide at least one test case that shows the feature working
3. Add documentation so that we can verify that the code seems to work as documented and vice versa

Done, please check the follow up commits.

I have a proposal for solving this slightly differently:

We introduce a new value to the existing CURLOPT_FRESH_CONNECT option. Currently this option uses the value 1 and means that this transfer should not reuse any existing connection. The current option basically just side-steps the existing connection cache.

What if we introduce a new value, (2) that means what when this transfer starts, it also marks all currently alive connections as not-for-reuse ? Because this functionality is so close to the existing option, I figure it might be an idea to use the same option and not having to create a new one.

What if we introduce a new value, (2) that means what when this transfer starts, it also marks all currently alive connections as not-for-reuse ? Because this functionality is so close to the existing option, I figure it might be an idea to use the same option and not having to create a new one.

I like that.

What if we introduce a new value, (2) that means what when this transfer starts, it also marks all currently alive connections as not-for-reuse ? Because this functionality is so close to the existing option, I figure it might be an idea to use the same option and not having to create a new one.

Oh, I have modified it: if set CURLOPT_FRESH_CONNECT=2, libcurl not only create a new connection for the current request, but also clear all existing connections in pool, for preventing follow-up requests reuse them.