curl/tests/data/test27

<testcase>
<info>
<keywords>
HTTP
HTTP GET
cookies
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 200 Mooo swsclose
Connection: close
Set-Cookie: thewinneris=nowayyouwin; path=/;
Content-Length: 8

*flopp*
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
Get same cookie page several times
 </name>
 <command>
"http://%HOSTIP:%HTTPPORT/want/{27,27,27}" -b none
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent: curl.*
</strip>
<protocol>
GET /want/27 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*

GET /want/27 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
Cookie: thewinneris=nowayyouwin

GET /want/27 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
Cookie: thewinneris=nowayyouwin

</protocol>
</verify>
</testcase>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`<testcase>`
keywords added 2005-04-16 19:15:19 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`cookies`
			`</keywords>`
			`</info>`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00			`# Server-side`
			`<reply>`
			`<data>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`HTTP/1.1 200 Mooo swsclose`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00			`Connection: close`
cookies: first n/v pair in Set-Cookie: is the cookie, then parameters RFC 6265 section 4.1.1 spells out that the first name/value pair in the header is the actual cookie name and content, while the following are the parameters. libcurl previously had a more liberal approach which causes significant problems when introducing new cookie parameters, like the suggested new cookie priority draft. The previous logic read all n/v pairs from left-to-right and the first name used that wassn't a known parameter name would be used as the cookie name, thus accepting "Set-Cookie: Max-Age=2; person=daniel" to be a cookie named 'person' while an RFC 6265 compliant parser should consider that to be a cookie named 'Max-Age' with an (unknown) parameter 'person'. Fixes #709 2016-03-10 05:20:56 -05:00			`Set-Cookie: thewinneris=nowayyouwin; path=/;`
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring. 2006-11-25 08:32:04 -05:00			`Content-Length: 8`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00
			`flopp`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
Each test case now specifies which server(s) it needs, without relying on the test number. 2003-04-30 16:25:39 -04:00			`<server>`
			`http`
			`</server>`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00			`<name>`
			`Get same cookie page several times`
			`</name>`
			`<command>`
Use double quotes in command lines for consistency. 2007-09-18 16:41:20 -04:00			`"http://%HOSTIP:%HTTPPORT/want/{27,27,27}" -b none`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent: curl.*`
			`</strip>`
			`<protocol>`
			`GET /want/27 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00
			`GET /want/27 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00			`Cookie: thewinneris=nowayyouwin`

			`GET /want/27 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
test case 27 added, to make sure cookie replacing don't leak anything 2001-10-24 07:39:48 -04:00			`Cookie: thewinneris=nowayyouwin`

			`</protocol>`
			`</verify>`
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools. 2007-01-22 21:25:56 -05:00			`</testcase>`