multi, signal network changed

A modified version of #17246 for signalling changes in network:

New multi option `CURLMOPT_NETWORK_CHANGED` with a long value:
0 - does nothing
1 - do not reuse existing connections
2 - as 1, but also clear DNS cache

One could also make the long a bitmask, if people want more control.

Documentation to be added if this gets the vote to go forward.
This commit is contained in:
Stefan Eissing 2025-06-13 12:38:44 +02:00
parent 7b8594176d
commit b1e6bae277
No known key found for this signature in database
14 changed files with 257 additions and 4 deletions

View file

@ -273,7 +273,7 @@ test3000 test3001 test3002 test3003 test3004 test3005 test3006 test3007 \
test3008 test3009 test3010 test3011 test3012 test3013 test3014 test3015 \
test3016 test3017 test3018 test3019 test3020 test3021 test3022 test3023 \
test3024 test3025 test3026 test3027 test3028 test3029 test3030 test3031 \
test3032 \
test3032 test3033 \
\
test3100 test3101 test3102 test3103 test3104 test3105 \
\

53
tests/data/test3033 Normal file
View file

@ -0,0 +1,53 @@
<testcase>
<info>
<keywords>
curl_easy_setopt
connection reuse
libtest
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Content-Length: 6
-foo-
</data>
<datacheck>
[0] no network change
-foo-
[1] signal network change
-foo-
[2] no network change
-foo-
</datacheck>
</reply>
#
# Client-side
<client>
<server>
http
</server>
<name>
CURLOPT_FRESH_CONNECT=2
</name>
<tool>
lib%TESTNUMBER
</tool>
<command>
http://%HOSTIP:%HTTPPORT/%TESTNUMBER
</command>
</client>
#
# Verify data after the test has been "shot"
<verify>
<errorcode>
0
</errorcode>
</verify>
</testcase>