| <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/%TESTNUMBER --fail |
| </command> |
| </client> |
| |
| # Verify data after the test has been "shot" |
| <verify> |
| <protocol> |
| GET /%TESTNUMBER HTTP/1.1
|
| Host: %HOSTIP:%HTTPPORT
|
| User-Agent: curl/%VERSION
|
| Accept: */*
|
|
|
| </protocol> |
| <errorcode> |
| 22 |
| </errorcode> |
| </verify> |
| </testcase> |
