curl/tests/data/test62

<testcase>
<info>
<keywords>
HTTP
HTTP GET
HTTP replaced headers
cookies
</keywords>
</info>

# Server-side
<reply>
<data>
HTTP/1.0 200 OK swsclose
Date: Thu, 09 Nov 2010 14:49:00 GMT
Content-Type: text/html

boo
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP, send cookies when using custom Host:
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/want/62 -b log/jar62.txt -H "Host: www.host.foo.com"
</command>
<file name="log/jar62.txt">
# 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
.fake.host.foo.com	TRUE	/we/want/	FALSE	2054030187	test4	yes

.foo.com	TRUE	/moo	TRUE	0	test3	maybe
</file>
</client>

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

</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-23 10:25:56 +08:00			`<testcase>`
keywords added 2005-04-23 05:59:08 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`HTTP replaced headers`
Added some <keywords> sections and use some key words more consistently. 2007-10-12 09:44:22 +08:00			`cookies`
keywords added 2005-04-23 05:59:08 +08:00			`</keywords>`
			`</info>`
Added some <keywords> sections and use some key words more consistently. 2007-10-12 09:44:22 +08:00
send correct cookies when using a custom Host: 2003-05-02 17:12:26 +08:00			`# Server-side`
			`<reply>`
			`<data>`
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 21:32:04 +08:00			`HTTP/1.0 200 OK swsclose`
send correct cookies when using a custom Host: 2003-05-02 17:12:26 +08:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Content-Type: text/html`

			`boo`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP, send cookies when using custom Host:`
			`</name>`
			`<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 16:08:38 +08:00			`http://%HOSTIP:%HTTPPORT/we/want/62 -b log/jar62.txt -H "Host: www.host.foo.com"`
send correct cookies when using a custom Host: 2003-05-02 17:12:26 +08:00			`</command>`
			`<file name="log/jar62.txt">`
			`# 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-28 05:00:45 +08:00			`# http://curlm.haxx.se/rfc/cookie_spec.html`
send correct cookies when using a custom Host: 2003-05-02 17:12:26 +08: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 10:38:25 +08:00			`.foo.com TRUE /we/want/ FALSE 2054030187 test yes`
			`.host.foo.com TRUE /we/want/ FALSE 2054030187 test2 yes`
			`.fake.host.foo.com TRUE /we/want/ FALSE 2054030187 test4 yes`
send correct cookies when using a custom Host: 2003-05-02 17:12:26 +08:00
			`.foo.com TRUE /moo TRUE 0 test3 maybe`
			`</file>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /we/want/62 HTTP/1.1`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 20:46:41 +08:00			`Accept: /`
send correct cookies when using a custom Host: 2003-05-02 17:12:26 +08:00			`Cookie: test2=yes; test=yes`
			`Host: www.host.foo.com`

			`</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-23 10:25:56 +08:00			`</testcase>`