curl-curl/tests/data/test554
Viktor Szakats 904e7ecb66
tests: replace remaining CR bytes with the new macro %CR
There is no more mixed-newline file in the repository after this patch.
Except for`.bat` and `.sln` files (4 in total), all files use LF
newlines.

Also:
- `spacecheck.pl`: drop mixed-EOL exception for test data.
- runtests: add option `-w` to check if test data has stray CR bytes in
  them.
- build: enable the option above in test targets, except the CI-specific
  one where `spacecheck.pl` does this job already.
- tested OK (with expected failures) in CI with stray CRs added.
- cmake: enable option `-a` for the `tests` target. To continue testing
  after a failed test.

Follow-up to 63e9721b63 #19313
Follow-up to 6cf3d7b1b1 #19318
Follow-up to 4d2a05d3fe #19284

Closes #19347
2025-11-06 20:45:45 +01:00

137 lines
3.1 KiB
Plaintext

<testcase>
<info>
<keywords>
HTTP
HTTP POST
FORM
</keywords>
</info>
#
# Server-side
<reply>
<data crlf="headers">
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Connection: close
Content-Type: text/html
hello
</data>
<datacheck crlf="headers">
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Connection: close
Content-Type: text/html
hello
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake swsclose
Connection: close
Content-Type: text/html
hello
</datacheck>
</reply>
# Client-side
<client>
<features>
form-api
</features>
<server>
http
</server>
# tool is what to use instead of 'curl'
<tool>
lib%TESTNUMBER
</tool>
<name>
HTTP multi-part formpost using read callback for the file part
</name>
<command>
http://%HOSTIP:%HTTPPORT/%TESTNUMBER
</command>
</client>
#
# Verify data after the test has been "shot"
<verify>
<strippart>
s/^--------------------------[A-Za-z0-9]*/------------------------------/
s/boundary=------------------------[A-Za-z0-9]*/boundary=----------------------------/
</strippart>
# Note that the stripping above removes 12 bytes from every occurrence of the
# boundary string and since 5 of them are in the body contents, we see
# (5*12) == 60 bytes less
<protocol>
POST /%TESTNUMBER HTTP/1.1%CR
Host: %HOSTIP:%HTTPPORT%CR
Accept: */*%CR
Content-Length: 780%CR
Content-Type: multipart/form-data; boundary=----------------------------%CR
%CR
------------------------------%CR
Content-Disposition: form-data; name="sendfile"; filename="postit2.c"%CR
%CR
this is what we post to the silly web server
%CR
------------------------------%CR
Content-Disposition: form-data; name="callbackdata"%CR
%CR
this is what we post to the silly web server
%CR
------------------------------%CR
Content-Disposition: form-data; name="filename"%CR
%CR
postit2.c%CR
------------------------------%CR
Content-Disposition: form-data; name="submit"%CR
Content-Type: text/plain%CR
%CR
send%CR
------------------------------%CR
Content-Disposition: form-data; name="somename"; filename="somefile.txt"%CR
Content-Type: text/plain%CR
%CR
blah blah%CR
--------------------------------%CR
POST /%TESTNUMBER HTTP/1.1%CR
Host: %HOSTIP:%HTTPPORT%CR
Accept: */*%CR
Content-Length: 794%CR
Content-Type: multipart/form-data; boundary=----------------------------%CR
%CR
------------------------------%CR
Content-Disposition: form-data; name="sendfile alternative"; filename="file name 2"%CR
%CR
this is what we post to the silly web server
%CR
------------------------------%CR
Content-Disposition: form-data; name="callbackdata"%CR
%CR
this is what we post to the silly web server
%CR
------------------------------%CR
Content-Disposition: form-data; name="filename"%CR
%CR
postit2.c%CR
------------------------------%CR
Content-Disposition: form-data; name="submit"%CR
Content-Type: text/plain%CR
%CR
send%CR
------------------------------%CR
Content-Disposition: form-data; name="somename"; filename="somefile.txt"%CR
Content-Type: text/plain%CR
%CR
blah blah%CR
--------------------------------%CR
</protocol>
</verify>
</testcase>