curl/tests/data/test75

<info>
<keywords>
HTTP
HTTP GET
FAILURE
</keywords>
</info>
#
# Server-side
<reply>
</reply>

#
# Client-side
<client>
<server>
none
</server>
 <name>
HTTP, urlglob retrieval with bad range
 </name>
 <command option=no-output>
"http://%HOSTIP:%HTTPPORT/[1-1]" -o "log/weee#1.dump" --stderr -
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<strip>
^User-Agent:.*
</strip>
<errorcode>
3
</errorcode>
<stdout mode=text>
curl: (3) [globbing] error: bad range specification after pos 24

</stdout>
</verify>
keywords added 2005-04-22 17:59:08 -04:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP GET`
			`FAILURE`
			`</keywords>`
			`</info>`
more tests 2003-08-06 19:45:59 -04:00			`#`
			`# Server-side`
			`<reply>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`none`
			`</server>`
			`<name>`
			`HTTP, urlglob retrieval with bad range`
			`</name>`
			`<command option=no-output>`
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/[1-1]" -o "log/weee#1.dump" --stderr -`
more tests 2003-08-06 19:45:59 -04:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^User-Agent:.*`
			`</strip>`
			`<errorcode>`
			`3`
			`</errorcode>`
Add support for text mode on stdout tests as well, and add the mode=text to the docs. 2005-05-20 06:40:32 -04:00			`<stdout mode=text>`
modified to the new error text for range error 2005-11-10 17:22:38 -05:00			`curl: (3) [globbing] error: bad range specification after pos 24`
more tests 2003-08-06 19:45:59 -04:00
			`</stdout>`
			`</verify>`