curl/tests/data/test97

<testcase>
<info>
<keywords>
HTTP
HTTP POST
HTTP replaced headers
</keywords>
</info>
#
# Server-side
<reply>
<data>
HTTP/1.0 200 OK
Server: test-server/fake
Content-Type: text/html
Content-Length: 6

blaha
</data>
</reply>

#
# Client-side
<client>
<server>
http
</server>
 <name>
HTTP POST with custom content-type
 </name>
 <command>
 -d "hejsanallabarn" -H "Content-Type: silly/type" http://%HOSTIP:%HTTPPORT/97
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<protocol nonewline="yes">
POST /97 HTTP/1.1
Host: 127.0.0.1:%HTTPPORT
Accept: */*
Content-Type: silly/type
Content-Length: 14

hejsanallabarn
</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>`
keyword update 2005-04-27 05:59:47 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP POST`
			`HTTP replaced headers`
			`</keywords>`
			`</info>`
added test 97, a simple test with -d post and a replacede content-type header using -H 2004-02-02 02:13:29 -05:00			`#`
			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.0 200 OK`
			`Server: test-server/fake`
			`Content-Type: text/html`
			`Content-Length: 6`

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

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP POST with custom content-type`
			`</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			`-d "hejsanallabarn" -H "Content-Type: silly/type" http://%HOSTIP:%HTTPPORT/97`
added test 97, a simple test with -d post and a replacede content-type header using -H 2004-02-02 02:13:29 -05:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
added test 97, a simple test with -d post and a replacede content-type header using -H 2004-02-02 02:13:29 -05:00
			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
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			`<protocol nonewline="yes">`
added test 97, a simple test with -d post and a replacede content-type header using -H 2004-02-02 02:13:29 -05:00			`POST /97 HTTP/1.1`
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			`Host: 127.0.0.1:%HTTPPORT`
Modified the default HTTP Accept: header to only be Accept: / 2004-02-09 07:46:41 -05:00			`Accept: /`
stricter newline policy 2004-11-29 07:01:07 -05:00			`Content-Type: silly/type`
			`Content-Length: 14`

added test 97, a simple test with -d post and a replacede content-type header using -H 2004-02-02 02:13:29 -05:00			`hejsanallabarn`
			`</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>`