mirror of
https://github.com/curl/curl.git
synced 2026-06-13 18:05:37 +03:00
244834d3a1
... 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
46 lines
797 B
XML
46 lines
797 B
XML
<?xml version="1.0" encoding="US-ASCII"?>
|
|
<testcase>
|
|
<info>
|
|
<keywords>
|
|
netrc
|
|
--resolve
|
|
</keywords>
|
|
</info>
|
|
|
|
<reply>
|
|
<data>
|
|
HTTP/1.1 200 OK
|
|
Content-Length: 6
|
|
|
|
12345
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
netrc parsing without user match but user in URL
|
|
</name>
|
|
<command>
|
|
--netrc --netrc-file %LOGDIR/netrc%TESTNUMBER http://alice@example.com:%HTTPPORT/%TESTNUMBER --resolve example.com:%HTTPPORT:%HOSTIP
|
|
</command>
|
|
<file name="%LOGDIR/netrc%TESTNUMBER" >
|
|
machine example.com login bob password sekret
|
|
</file>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol crlf="headers">
|
|
GET /%TESTNUMBER HTTP/1.1
|
|
Host: example.com:%HTTPPORT
|
|
Authorization: Basic %b64[alice:]b64%
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|