Skip to content

Conversation

@bagder
Copy link
Member

@bagder bagder commented Jan 14, 2025

This typically happens if CURL_CONNECT_ONLY is used and a second curl_easy_perform() is attempted.

A connection "taken over" with CURL_CONNECT_ONLY cannot be ended any other way than a curl_easy_cleanup() on the easy handle that holds it.

Add test 696 to verify.

This typically happens if CURL_CONNECT_ONLY is used and a second
curl_easy_perform() is attempted.

A connection "taken over" with CURL_CONNECT_ONLY cannot be ended any
other way than a curl_easy_cleanup() on the easy handle that holds it.

Add test 696 to verify.
@bagder bagder closed this in be82a36 Jan 14, 2025
@bagder bagder deleted the bagder/connect-only-double-perform branch January 14, 2025 15:33
pps83 pushed a commit to pps83/curl that referenced this pull request Apr 26, 2025
This typically happens if CURL_CONNECT_ONLY is used and a second
curl_easy_perform() is attempted.

A connection "taken over" with CURL_CONNECT_ONLY cannot be ended any
other way than a curl_easy_cleanup() on the easy handle that holds it.

Add test 696 to verify.

Closes curl#16003
vszakats added a commit to vszakats/curl that referenced this pull request Nov 2, 2025
Test 696 and 556 share the same libtest code. Make sure to issue
the `GET` request to the correct test number. It makes the `sws` test
server read the response string from `test696` `<data>` section, instead
of reading it from `test556`. To avoid this hidden interaction between
test data.

AFAICS there is no other similar hardcoded string in reused libtests.

Ref: curl#19313 (comment)

Follow-up to be82a36 curl#16003
vszakats added a commit that referenced this pull request Nov 3, 2025
Test 696 and 556 share the same libtest code. Make sure to issue
the `GET` request to the correct runtime test number instead of using
the hard-wired "556".

It makes the `sws` test server read the response string from `test696`
`<data>` section, instead of reading it from `test556`. To avoid this
hidden interaction between test data.

AFAICS there is no other similar hard-coded string in reused libtests.

Ref: #19313 (comment)
Follow-up to be82a36 #16003
Closes #19329
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.

1 participant