curl/tests/data/test152

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

# Server-side
<reply>
<data nocheck="yes">
HTTP/1.0 401 BAD BOY
Server: swsclose
Content-Type: text/html

This contains a response code >= 400, so curl shouldn't display this.  Even
though it's a response code that triggers authentication, we're not using
authentication so we should still fail.
</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP GET with an error code that might trick authentication and --fail
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/152 --fail
</command>
</client>

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

</protocol>
<errorcode>
22
</errorcode>
</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>`
tests: add keywords for a couple of HTTP tests 2012-11-19 11:54:52 -05:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`--fail`
			`</keywords>`
			`</info>`

David Byron's new test cases for the --fail and auth stuff. 2004-03-30 01:41:33 -05:00			`# Server-side`
			`<reply>`
Always use nocheck="yes" for consistency 2009-01-07 16:57:26 -05:00			`<data nocheck="yes">`
David Byron's new test cases for the --fail and auth stuff. 2004-03-30 01:41:33 -05:00			`HTTP/1.0 401 BAD BOY`
			`Server: swsclose`
			`Content-Type: text/html`

			`This contains a response code >= 400, so curl shouldn't display this. Even`
			`though it's a response code that triggers authentication, we're not using`
			`authentication so we should still fail.`
			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP GET with an error code that might trick authentication and --fail`
			`</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/152 --fail`
David Byron's new test cases for the --fail and auth stuff. 2004-03-30 01:41:33 -05:00			`</command>`
A minor "syntax error" in numerous test files corrected 2005-01-25 16:45:03 -05:00			`</client>`
David Byron's new test cases for the --fail and auth stuff. 2004-03-30 01:41:33 -05:00
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`GET /152 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`
David Byron's new test cases for the --fail and auth stuff. 2004-03-30 01:41:33 -05:00			`Accept: /`

			`</protocol>`
			`<errorcode>`
			`22`
			`</errorcode>`
			`</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>`