2007-01-22 21:25:56 -05:00
|
|
|
<testcase>
|
2012-11-19 11:54:52 -05:00
|
|
|
<info>
|
|
|
|
|
<keywords>
|
|
|
|
|
HTTP
|
|
|
|
|
HTTP GET
|
|
|
|
|
</keywords>
|
|
|
|
|
</info>
|
|
|
|
|
|
2004-03-30 01:41:33 -05:00
|
|
|
# Server-side
|
|
|
|
|
<reply>
|
|
|
|
|
<data>
|
|
|
|
|
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
|
|
|
|
|
</name>
|
|
|
|
|
<command>
|
2021-03-12 11:38:26 -05:00
|
|
|
http://%HOSTIP:%HTTPPORT/%TESTNUMBER
|
2004-03-30 01:41:33 -05:00
|
|
|
</command>
|
2005-01-25 16:45:03 -05:00
|
|
|
</client>
|
2004-03-30 01:41:33 -05:00
|
|
|
|
|
|
|
|
# Verify data after the test has been "shot"
|
|
|
|
|
<verify>
|
|
|
|
|
<protocol>
|
2021-03-12 11:38:26 -05:00
|
|
|
GET /%TESTNUMBER HTTP/1.1
|
2007-09-14 15:32:31 -04:00
|
|
|
Host: %HOSTIP:%HTTPPORT
|
2020-10-02 07:45:24 -04:00
|
|
|
User-Agent: curl/%VERSION
|
2004-03-30 01:41:33 -05:00
|
|
|
Accept: */*
|
|
|
|
|
|
|
|
|
|
</protocol>
|
|
|
|
|
</verify>
|
2007-01-22 21:25:56 -05:00
|
|
|
</testcase>
|
