<testcase> # 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> <strip> ^User-Agent: curl/.* </strip> <protocol> GET /152 HTTP/1.1 User-Agent: curl/7.8.1-pre3 (sparc-sun-solaris2.7) libcurl 7.8.1-pre3 (OpenSSL 0.9.6a) (krb4 enabled) Host: %HOSTIP:%HTTPPORT Accept: */* </protocol> <errorcode> 22 </errorcode> </verify> </testcase>