curl/tests/data/test2503
Fabian Keil 244834d3a1
tests: add the "--resolve" keyword to tests that lack it
... even though they use the curl option "--resolve".

This makes it more convenient to choose or skip the tests.

For example Privoxy's cts test framework relies on the "--resolve"
keyword when executing the "upstream-tests" scenario to skip curl
tests that aren't expected to work when the requests are made through
Privoxy. While some of the modified tests are already skipped for
other reasons through other means when testing Privoxy, it's good to
be consistent.

Closes #21930
2026-06-11 23:10:16 +02:00

71 lines
1.1 KiB
XML

<?xml version="1.0" encoding="US-ASCII"?>
<testcase>
<info>
<keywords>
HTTP
HTTP/3
HTTPS
--resolve
-w
%header
</keywords>
</info>
# Server-side
<reply>
<data crlf="headers" nocheck="yes">
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 14:49:00 GMT
Content-Length: 6
Connection: close
Content-Type: text/html
Funny-head: yesyes
-foo-
</data>
</reply>
# Client-side
<client>
<features>
http/3
nghttpx-h3
headers-api
</features>
<server>
http/3
</server>
<name>
HTTP/3 header-api
</name>
<setenv>
</setenv>
<command>
-w '%{header_json}\n' --http3-only --cacert %CERTDIR/certs/test-ca.crt --resolve localhost:%HTTP3PORT:%HOSTIP https://localhost:%HTTP3PORT/%TESTNUMBER
</command>
</client>
# Verify data after the test has been "shot"
<verify>
<stdout crlf="headers">
HTTP/3 200%SP
date: Tue, 09 Nov 2010 14:49:00 GMT
content-length: 6
content-type: text/html
funny-head: yesyes
via: 1.1 nghttpx
-foo-
{"date":["Tue, 09 Nov 2010 14:49:00 GMT"],
"content-length":["6"],
"content-type":["text/html"],
"funny-head":["yesyes"],
"via":["1.1 nghttpx"]
}
</stdout>
<limits>
Maximum allocated: 1800000
</limits>
</verify>
</testcase>