curl/tests/data/test42

<testcase>
<info>
<keywords>
HTTP
HTTP GET
followlocation
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.1 302 OK swsclose
Location: ../m o o.html/420002    
Date: Thu, 09 Nov 2010 14:49:00 GMT
Connection: close

</data>
<data2>
HTTP/1.1 200 OK swsclose
Location: this should be ignored
Date: Thu, 09 Nov 2010 14:49:00 GMT
Connection: close

body
</data2>
<datacheck>
HTTP/1.1 302 OK swsclose
%if !hyper
Location: ../m o o.html/420002    
%else
Location: ../m o o.html/420002
%endif
Date: Thu, 09 Nov 2010 14:49:00 GMT
Connection: close

HTTP/1.1 200 OK swsclose
Location: this should be ignored
Date: Thu, 09 Nov 2010 14:49:00 GMT
Connection: close

body
</datacheck>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP redirect with whitespace in path (and conversion)
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/we/are/all/twits/42 -L
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /we/are/all/twits/42 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*

GET /we/are/all/m%20o%20o.html/420002 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*

</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-22 21:25:56 -05:00			`<testcase>`
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`followlocation`
			`</keywords>`
			`</info>`
new tests 2003-06-26 07:45:04 -04:00			`#`
			`# Server-side`
			`<reply>`
			`<data>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`HTTP/1.1 302 OK swsclose`
new tests 2003-06-26 07:45:04 -04:00			`Location: ../m o o.html/420002`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Connection: close`

			`</data>`
			`<data2>`
Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this. 2012-11-14 13:49:12 -05:00			`HTTP/1.1 200 OK swsclose`
			`Location: this should be ignored`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Connection: close`

new tests 2003-06-26 07:45:04 -04:00			`body`
			`</data2>`
			`<datacheck>`
modified to work fine with the new persistant connection working test suite HTTP server 2003-07-19 19:57:08 -04:00			`HTTP/1.1 302 OK swsclose`
tests: updated tests for Hyper 2020-12-14 08:10:33 -05:00			`%if !hyper`
new tests 2003-06-26 07:45:04 -04:00			`Location: ../m o o.html/420002`
tests: updated tests for Hyper 2020-12-14 08:10:33 -05:00			`%else`
			`Location: ../m o o.html/420002`
			`%endif`
new tests 2003-06-26 07:45:04 -04:00			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Connection: close`

Do not mix CRLF and LF header endings in a couple of HTTP tests Consistently use CRLF instead. The mixed endings weren't documented so I assume they were unintentional. This change doesn't matter for curl itself but makes using the tests with a proxy between curl and the test server more convenient. Tests that consistently use no carriage returns were left unmodified as one can easily work around this. 2012-11-14 13:49:12 -05:00			`HTTP/1.1 200 OK swsclose`
			`Location: this should be ignored`
			`Date: Thu, 09 Nov 2010 14:49:00 GMT`
			`Connection: close`

new tests 2003-06-26 07:45:04 -04:00			`body`
			`</datacheck>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP redirect with whitespace in path (and conversion)`
			`</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 04:08:38 -04:00			`http://%HOSTIP:%HTTPPORT/we/are/all/twits/42 -L`
new tests 2003-06-26 07:45:04 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`GET /we/are/all/twits/42 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04: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 07:45:24 -04:00			`User-Agent: curl/%VERSION`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
new tests 2003-06-26 07:45:04 -04:00
			`GET /we/are/all/m%20o%20o.html/420002 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04: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 07:45:24 -04:00			`User-Agent: curl/%VERSION`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
new tests 2003-06-26 07:45:04 -04:00
			`</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-22 21:25:56 -05:00			`</testcase>`