curl/tests/data/test512

<testcase>
<info>
<keywords>
HTTP
HTTP GET
</keywords>
</info>

#
# Server-side
<reply>
<data>
HTTP/1.1 200 OK swsclose
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: yes
Connection: close

hello
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
# tool is what to use instead of 'curl'
<tool>
lib512
</tool>

 <name>
simple curl_easy_duplicate() test
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/512
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
GET /512 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
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-23 10:25:56 +08:00			`<testcase>`
tests: add keywords for a couple of HTTP tests 2012-11-20 00:54:52 +08:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`</keywords>`
			`</info>`

test 512 does some basic curl_easy_duphandle() testing 2004-04-29 18:57:10 +08:00			`#`
			`# Server-side`
			`<reply>`
testsuite: use binary output mode for custom curl test tools Do not try to convert line-endings to CRLF on Windows by setting stdout to binary mode, just like the curl tool does if --ascii is not specified. This should prevent corrupted stdout line-ending output like CRCRLF. In order to make the previously naive text-aware tests work with binary mode on Windows, text-mode is disabled for them if it is not actually part of the test case and line-endings are corrected. 2014-02-01 07:58:58 +08:00			`<data>`
test 512 does some basic curl_easy_duphandle() testing 2004-04-29 18:57:10 +08:00			`HTTP/1.1 200 OK 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`
test 512 does some basic curl_easy_duphandle() testing 2004-04-29 18:57:10 +08:00			`Server: yes`
			`Connection: close`

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

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`# tool is what to use instead of 'curl'`
			`<tool>`
			`lib512`
			`</tool>`

			`<name>`
			`simple curl_easy_duplicate() test`
			`</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/512`
test 512 does some basic curl_easy_duphandle() testing 2004-04-29 18:57:10 +08:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`GET /512 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-15 03:32:31 +08:00			`Host: %HOSTIP:%HTTPPORT`
test 512 does some basic curl_easy_duphandle() testing 2004-04-29 18:57:10 +08:00			`Accept: /`

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