curl/tests/data/test249

<testcase>
<info>
<keywords>
HTTP
HTTP GET
-z
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.1 304 Not Modified swsclose
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Last-Modified: Tue, 13 Jun 1910 12:10:00 GMT
ETag: "21025-dc7-39462498"
Accept-Ranges: bytes
Content-Length: 677777
Connection: close
Content-Type: text/html

</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP 304 response with "illegal" Content-Length: header
</name>
<command>
http://%HOSTIP:%HTTPPORT/%TESTNUMBER -z "dec 12 12:00:00 1999 GMT"
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
If-Modified-Since: Sun, 12 Dec 1999 12: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>`
Add keywords for a couple of currently keyword-less HTTP tests 2012-11-13 21:02:42 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
tests: Add some missing keywords to tests These are needed to skip some tests when configure options have disabled certain features. 2021-12-01 10:32:53 +08:00			`-z`
Add keywords for a couple of currently keyword-less HTTP tests 2012-11-13 21:02:42 +08:00			`</keywords>`
			`</info>`
fixed the 304 response-with-content-length problem reported by Cory Nelson 2005-04-09 00:59:13 +08:00			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 304 Not Modified swsclose`
tests: fixup several tests missing CRs and modified %hostip lib556/test556: use a real HTTP version to make test reuse more convenient make sure the weekday in Date headers matches the date test61: replace stray "^M" (5e 4d) at the end of a cookie with a '^M' (0d) Gets the test working with external proxies like Privoxy again. Closes #6463 2020-02-28 22:00:03 +08:00			`Date: Tue, 09 Nov 2010 14:49:00 GMT`
fixed the 304 response-with-content-length problem reported by Cory Nelson 2005-04-09 00:59:13 +08:00			`Server: test-server/fake`
			`Last-Modified: Tue, 13 Jun 1910 12:10:00 GMT`
			`ETag: "21025-dc7-39462498"`
			`Accept-Ranges: bytes`
			`Content-Length: 677777`
			`Connection: close`
			`Content-Type: text/html`

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

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`<name>`
fixed the 304 response-with-content-length problem reported by Cory Nelson 2005-04-09 00:59:13 +08:00			`HTTP 304 response with "illegal" Content-Length: header`
tests: remove leading spaces from some tags The threee tags `<name>`, `</name>` and `<command>` were frequently used with a leading space that this removes. The reason this habbit is so widespread in testcases is probably that they have been copy and pasted. Hence, fixing them all now might curb this practice from now on. Closes #12028 2023-10-04 17:35:54 +08:00			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`http://%HOSTIP:%HTTPPORT/%TESTNUMBER -z "dec 12 12:00:00 1999 GMT"`
fixed the 304 response-with-content-length problem reported by Cory Nelson 2005-04-09 00:59:13 +08:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-13 00:38:26 +08:00			`GET /%TESTNUMBER HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 2020-10-02 19:45:24 +08:00			`User-Agent: curl/%VERSION`
fixed the 304 response-with-content-length problem reported by Cory Nelson 2005-04-09 00:59:13 +08:00			`Accept: /`
			`If-Modified-Since: Sun, 12 Dec 1999 12: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>`