moparisthebest/curl
1
0
Fork 0
mirror of https://github.com/moparisthebest/curl synced 2024-11-10 19:45:04 -05:00
Code Issues Releases Wiki Activity
3b05f79ef8
curl/tests/data/test173

85 lines
1.4 KiB
Plaintext
Raw Normal View History

Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => & ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-22 21:25:56 -05:00
<testcase>
Fixed a NULL pointer dereference in form posting It was introduced in commit eeb2cb05 along with the -F type= change. Also fixed a typo in the name of the magic filename= parameter. Tweaked tests 39 and 173 to better test this path.
2010-08-24 19:45:31 -04:00
<info>
<keywords>
HTTP
HTTP POST
</keywords>
</info>
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
# Server-side
<reply>
<data>
HTTP/1.1 200 OK swsclose
Date: Thu, 09 Nov 2010 14:49:00 GMT
Server: test-server/fake
Venkat Akella found out that libcurl did not like HTTP responses that simply responded with a single status line and no headers nor body. Starting now, a HTTP response on a persistent connection (i.e not set to be closed after the response has been taken care of) must have Content-Length or chunked encoding set, or libcurl will simply assume that there is no body. To my horror I learned that we had no less than 57(!) test cases that did bad HTTP responses like this, and even the test http server (sws) responded badly when queried by the test system if it is the test system. So although the actual fix for the problem was tiny, going through all the newly failing test cases got really painful and boring.
2006-11-25 08:32:04 -05:00
Content-Length: 11
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
blablabla
</data>
</reply>
# Client-side
<client>
<server>
http
</server>
<name>
HTTP RFC1867-formpost a file from stdin with "faked" filename
</name>
<command>
Fixed a NULL pointer dereference in form posting It was introduced in commit eeb2cb05 along with the -F type= change. Also fixed a typo in the name of the magic filename= parameter. Tweaked tests 39 and 173 to better test this path.
2010-08-24 19:45:31 -04:00
http://%HOSTIP:%HTTPPORT/we/want/173 -F field1=contents1 -F "fileupload=@-;filename=/dev/null;type=text/x-null;format=x-curl"
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
</command>
<stdin>
line1
line2
line3
line4
line5
line6
line7
line8
</stdin>
</client>
# Verify data after the test has been "shot"
<verify>
<strip>
^(User-Agent:|Content-Type: multipart/form-data;|------------).*
</strip>
<protocol>
POST /we/want/173 HTTP/1.1
User-Agent: curl/7.12.1-CVS (i686-pc-linux-gnu) libcurl/7.12.1-CVS OpenSSL/0.9.6b ipv6 zlib/1.1.4 GSS libidn/0.4.6
Replaced 127.0.0.1 with %HOSTIP where possible
2007-09-14 15:32:31 -04:00
Host: %HOSTIP:%HTTPPORT
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
Accept: */*
mime: remove support "-" stdin pseudo-file name in curl_mime_filedata(). This feature is badly supported in Windows: as a replacement, a caller has to use curl_mime_data_cb() with fread, fseek and possibly fclose callbacks to process opened files. The cli tool and documentation are updated accordingly. The feature is however kept internally for form API compatibility, with the known caveats it always had. As a side effect, stdin size is not determined by the cli tool even if possible and this results in a chunked transfer encoding. Test 173 is updated accordingly.
2017-09-03 09:45:43 -04:00
Transfer-Encoding: chunked
Expect: 100-continue
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
Content-Type: multipart/form-data; boundary=----------------------------5dbea401cd8c
mime: remove support "-" stdin pseudo-file name in curl_mime_filedata(). This feature is badly supported in Windows: as a replacement, a caller has to use curl_mime_data_cb() with fread, fseek and possibly fclose callbacks to process opened files. The cli tool and documentation are updated accordingly. The feature is however kept internally for form API compatibility, with the known caveats it always had. As a side effect, stdin size is not determined by the cli tool even if possible and this results in a chunked transfer encoding. Test 173 is updated accordingly.
2017-09-03 09:45:43 -04:00
168
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
------------------------------5dbea401cd8c
Content-Disposition: form-data; name="field1"
contents1
------------------------------5dbea401cd8c
Content-Disposition: form-data; name="fileupload"; filename="/dev/null"
Fixed a NULL pointer dereference in form posting It was introduced in commit eeb2cb05 along with the -F type= change. Also fixed a typo in the name of the magic filename= parameter. Tweaked tests 39 and 173 to better test this path.
2010-08-24 19:45:31 -04:00
Content-Type: text/x-null;format=x-curl
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
line1
line2
line3
line4
line5
line6
line7
line8
------------------------------5dbea401cd8c--
mime: remove support "-" stdin pseudo-file name in curl_mime_filedata(). This feature is badly supported in Windows: as a replacement, a caller has to use curl_mime_data_cb() with fread, fseek and possibly fclose callbacks to process opened files. The cli tool and documentation are updated accordingly. The feature is however kept internally for form API compatibility, with the known caveats it always had. As a side effect, stdin size is not determined by the cli tool even if possible and this results in a chunked transfer encoding. Test 173 is updated accordingly.
2017-09-03 09:45:43 -04:00
0
test 173 added: HTTP RFC1867-formpost a file from stdin with "faked" filename
2004-06-04 08:24:47 -04:00
</protocol>
</verify>
Convert (most of) the test data files into genuine XML. A handful still are not, due mainly to the lack of support for XML character entities (e.g. & => &amp; ). This will make it easier to validate test files using tools like xmllint, as well as edit and view them using XML tools.
2007-01-22 21:25:56 -05:00
</testcase>
Reference in New Issue Copy Permalink