curl/tests/data/test78

<testcase>
<info>
<keywords>
HTTP
HTTP GET
-z
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK
Server: test-server/fake
Last-Modified: Tue, 13 Jun 1990 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 6
Connection: close
Content-Type: text/html
Funny-head: yesyes

-foo-
</data>
<datacheck>
HTTP/1.1 200 OK
Server: test-server/fake
Last-Modified: Tue, 13 Jun 1990 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 6
Connection: close
Content-Type: text/html
Funny-head: yesyes

</datacheck>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP with -z "newer date"
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/78 -z "dec 12 11:00:00 1999 GMT"
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol>
GET /78 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
Accept: */*
If-Modified-Since: Sun, 12 Dec 1999 11:00:00 GMT

</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`
			`-z`
			`</keywords>`
			`</info>`
new -z tests 2003-08-08 16:13:11 +08:00			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 200 OK`
			`Server: test-server/fake`
			`Last-Modified: Tue, 13 Jun 1990 12:10:00 GMT`
			`ETag: "21025-dc7-39462498"`
			`Accept-Ranges: bytes`
			`Content-Length: 6`
			`Connection: close`
			`Content-Type: text/html`
			`Funny-head: yesyes`

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			`-foo-`
new -z tests 2003-08-08 16:13:11 +08:00			`</data>`
			`<datacheck>`
			`HTTP/1.1 200 OK`
			`Server: test-server/fake`
			`Last-Modified: Tue, 13 Jun 1990 12:10:00 GMT`
			`ETag: "21025-dc7-39462498"`
			`Accept-Ranges: bytes`
			`Content-Length: 6`
			`Connection: close`
			`Content-Type: text/html`
			`Funny-head: yesyes`

			`</datacheck>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP with -z "newer date"`
			`</name>`
			`<command>`
1. cookie expire-strings MUST use GMT timezones 2. adjusted date strings to upcoming date parser rewrite 2004-09-12 03:12:37 +08:00			`http://%HOSTIP:%HTTPPORT/78 -z "dec 12 11:00:00 1999 GMT"`
new -z tests 2003-08-08 16:13:11 +08:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<protocol>`
			`GET /78 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 20:46:41 +08:00			`Accept: /`
new -z tests 2003-08-08 16:13:11 +08:00			`If-Modified-Since: Sun, 12 Dec 1999 11:00:00 GMT`

			`</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>`