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://curl.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-23 03:25:56 +01:00			`<testcase>`
keywords added 2005-04-22 23:59:08 +02: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 21:49:51 +02: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-05 03:38:25 +01:00			`Set-Cookie: test=yes; domain=foo.com; expires=Fri Feb 2 11:56:27 GMT 2035`
Tweaked a few tests to test proper Turkish locale handling 2008-10-23 03:53:27 +02:00			`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 21:49:51 +02: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-20 01:57:08 +02:00			`Content-Length: 4`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02: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 22:25:39 +02:00			`<server>`
			`http`
			`</server>`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02: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-11 00:27:16 +02: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 21:49:51 +02: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 10:08:38 +02: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 21:49:51 +02:00			`</command>`
fixed the format slightly 2003-05-02 11:11:53 +02:00			`</client>`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02: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 13:46:41 +01:00			`Accept: /`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02: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-23 03:25:56 +01:00			`<file name="log/jar61.txt" mode="text">`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02:00			`# Netscape HTTP Cookie File`
- I'm abandoning the system with the web site mirrors (but keeping download files bing mirrored) and thus I've changed the URL in the cookiejar header to no longer use curlm.haxx.se but instead use the main site curl.haxx.se 2008-08-28 13:35:54 +02:00			`# http://curl.haxx.se/rfc/cookie_spec.html`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02: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-05 03:38:25 +01: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 21:56:53 +02:00			`.foo.com TRUE /moo TRUE 0 test3 maybe`
various new cookie tests with a custom Host: header set 2003-04-30 21:49:51 +02: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-23 03:25:56 +01:00			`</testcase>`