curl/tests/data/test61

<testcase>
<info>
<keywords>
HTTP
HTTP GET
cookies
cookiejar
HTTP replaced headers
</keywords>
</info>
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Content-Type: text/html
Funny-head: yesyes
Set-Cookie: test=yes; domain=foo.com; expires=Fri Feb 2 11:56:27 GMT 2035
Set-Cookie: test2=yes; domain=host.foo.com; expires=Fri Feb 2 11:56:27 GMT 2035
Set-Cookie: test3=maybe; domain=foo.com; path=/moo; secure
Set-Cookie: test4=no; domain=nope.foo.com; path=/moo; secure
Set-Cookie: test5=name; domain=anything.com; path=/ ; secure
Content-Length: 4

boo
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP with various cookies and custom Host:
 </name>
# Explicitly set the time zone to a known good one, in case the user is
# using one of the 'right' zones that take into account leap seconds
# which causes the cookie expiry times to be different.
<setenv>
TZ=GMT
</setenv>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/61 -c log/jar61.txt -H "Host: www.host.foo.com"
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /we/want/61 HTTP/1.1
Accept: */*
Host: www.host.foo.com

</protocol>
<file name="log/jar61.txt" mode="text">
# Netscape HTTP Cookie File
# http://curlm.haxx.se/rfc/cookie_spec.html
# This file was generated by libcurl! Edit at your own risk.

.foo.com	TRUE	/we/want/	FALSE	2054030187	test	yes
.host.foo.com	TRUE	/we/want/	FALSE	2054030187	test2	yes
.foo.com	TRUE	/moo	TRUE	0	test3	maybe
</file>
</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-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`cookies`
			`cookiejar`
			`HTTP replaced headers`
			`</keywords>`
			`</info>`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 OK`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Server: test-server/fake`
			`Content-Type: text/html`
			`Funny-head: yesyes`
Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035. 2007-02-04 21:38:25 -05:00			`Set-Cookie: test=yes; domain=foo.com; expires=Fri Feb 2 11:56:27 GMT 2035`
			`Set-Cookie: test2=yes; domain=host.foo.com; expires=Fri Feb 2 11:56:27 GMT 2035`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`Set-Cookie: test3=maybe; domain=foo.com; path=/moo; secure`
			`Set-Cookie: test4=no; domain=nope.foo.com; path=/moo; secure`
			`Set-Cookie: test5=name; domain=anything.com; path=/ ; secure`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`Content-Length: 4`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00
			`boo`
			`</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>`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`<name>`
			`HTTP with various cookies and custom Host:`
			`</name>`
Force the time zone to GMT in the cookie tests in case the user is using one of the so-called 'right' time zones that take into account leap seconds, which causes the tests to fail (as reported by Daniel Black in bug report #1745964). 2007-07-10 18:27:16 -04:00			`# Explicitly set the time zone to a known good one, in case the user is`
			`# using one of the 'right' zones that take into account leap seconds`
			`# which causes the cookie expiry times to be different.`
			`<setenv>`
			`TZ=GMT`
			`</setenv>`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`<command>`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 04:08:38 -04:00			`http://%HOSTIP:%HTTPPORT/we/want/61 -c log/jar61.txt -H "Host: www.host.foo.com"`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`</command>`
fixed the format slightly 2003-05-02 05:11:53 -04:00			`</client>`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /we/want/61 HTTP/1.1`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`Host: www.host.foo.com`

			`</protocol>`
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			`<file name="log/jar61.txt" mode="text">`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`# Netscape HTTP Cookie File`
As reported in bug: #1566077 the former URL mentioned in the generated cookie jar has died and we now instead point out our own version of that 2006-09-27 17:00:45 -04:00			`# http://curlm.haxx.se/rfc/cookie_spec.html`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`# This file was generated by libcurl! Edit at your own risk.`

Year 2038 has its own problems (32 bit integer overflow). So cookie expiration date is lowered to expire at most in 2035. 2007-02-04 21:38:25 -05:00			`.foo.com TRUE /we/want/ FALSE 2054030187 test yes`
			`.host.foo.com TRUE /we/want/ FALSE 2054030187 test2 yes`
ok, make the test run ok too 2003-04-30 15:56:53 -04:00			`.foo.com TRUE /moo TRUE 0 test3 maybe`
various new cookie tests with a custom Host: header set 2003-04-30 15:49:51 -04:00			`</file>`
			`</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>`