mirror of
https://github.com/curl/curl.git
synced 2026-06-13 15:05:38 +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
54 lines
856 B
XML
54 lines
856 B
XML
<?xml version="1.0" encoding="US-ASCII"?>
|
|
<testcase>
|
|
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP GET
|
|
--resolve
|
|
</keywords>
|
|
</info>
|
|
|
|
# Server-side
|
|
<reply>
|
|
<data crlf="headers">
|
|
HTTP/1.1 200 OK
|
|
Content-Length: 6
|
|
Set-Cookie: something=1; Domain=co.uk.; Path=/
|
|
|
|
-foo-
|
|
</data>
|
|
</reply>
|
|
|
|
# Client-side
|
|
<client>
|
|
<features>
|
|
PSL
|
|
cookies
|
|
</features>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
cookies with trailing dot after PSL domain
|
|
</name>
|
|
<command>
|
|
http://foo.co.uk.:%HTTPPORT/ http://bar.co.uk.:%HTTPPORT/ -b "" --resolve foo.co.uk.:%HTTPPORT:%HOSTIP --resolve bar.co.uk.:%HTTPPORT:%HOSTIP
|
|
</command>
|
|
</client>
|
|
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<protocol crlf="headers">
|
|
GET / HTTP/1.1
|
|
Host: foo.co.uk.:%HTTPPORT
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
|
|
GET / HTTP/1.1
|
|
Host: bar.co.uk.:%HTTPPORT
|
|
User-Agent: curl/%VERSION
|
|
Accept: */*
|
|
|
|
</protocol>
|
|
</verify>
|
|
</testcase>
|