curl/tests/data/test504
Dan Fandrich 5f5a7b478a tests: Stop referring to server ports when they're not used
Several tests referred to specific server ports even when the test
didn't actually use that server or specify that it's needed. In such
cases, the test harness substitutes the text "[not running]" as the port
number which causes many such tests to fail due to the inability to
parse the URL.  These tests are changed to use %NOLISTENPORT which will
always be substituted correctly.
2020-04-30 16:00:31 +02:00

47 lines
583 B
Plaintext

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP proxy
multi
FAILURE
connect to non-listen
</keywords>
</info>
# Server-side
<reply>
</reply>
# Client-side
<client>
<server>
none
</server>
<features>
http
proxy
</features>
# tool is what to use instead of 'curl'
<tool>
lib504
</tool>
<name>
simple multi through local proxy without listener
</name>
<command>
http://%HOSTIP:%NOLISTENPORT/504 %HOSTIP:%NOLISTENPORT
</command>
</client>
# Verify data after the test has been "shot"
# TEST_ERR_SUCCESS is errorcode 120
<verify>
<errorcode>
120
</errorcode>
</verify>
</testcase>