1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
<?xml version="1.0" encoding="US-ASCII"?>
<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 should not display this. Even
though it is a response code that triggers authentication, we are 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 crlf="headers">
GET /%TESTNUMBER HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
</protocol>
<errorcode>
22
</errorcode>
</verify>
</testcase>
|
