curl-curl/tests/data/test152
Viktor Szakats a87383828e
badwords: fix issues found in tests
There remain some false positives, hits in test data, and `dir` use,
around 100 issues in total.

There is no plan to enforce badwords on tests.

Also:
- badwords.txt: let a few `manpage[s]` occurrences through
  (in Perl code).

Closes #19541
2025-11-17 13:30:35 +01:00

50 lines
828 B
Plaintext

<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>