curl/tests/data/test158

<testcase>
<info>
<keywords>
HTTP
HTTP POST
</keywords>
</info>

# Server-side
<reply>
<data>
HTTP/1.1 100 Continue swsclose
Silly-header: yeeeees

</data>
</reply>

# Client-side
<client>
<server>
http
</server>
 <name>
HTTP multipart formpost with only a 100 reply
 </name>
 <command>
http://%HOSTIP:%HTTPPORT/158 -F name=daniel
</command>
</client>

# Verify data after the test has been "shot"
<verify>
<strip>
^Content-Type: multipart/form-data.*
^-----------------------.*
</strip>
<protocol>
POST /158 HTTP/1.1
Host: %HOSTIP:%HTTPPORT
User-Agent: curl/%VERSION
Accept: */*
Content-Length: 145
Content-Type: multipart/form-data; boundary=----------------------------4f12fcdaa3bc

------------------------------4f12fcdaa3bc
Content-Disposition: form-data; name="name"

daniel
------------------------------4f12fcdaa3bc--
</protocol>
<errorcode>
52
</errorcode>
</verify>
</testcase>
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>`
Add keywords for a couple of currently keyword-less HTTP tests 2012-11-13 08:02:42 -05:00			`<info>`
			`<keywords>`
			`HTTP`
			`HTTP POST`
			`</keywords>`
			`</info>`

getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 10:27:54 -04:00			`# Server-side`
			`<reply>`
			`<data>`
			`HTTP/1.1 100 Continue swsclose`
			`Silly-header: yeeeees`

			`</data>`
			`</reply>`

			`# Client-side`
			`<client>`
			`<server>`
			`http`
			`</server>`
			`<name>`
			`HTTP multipart formpost with only a 100 reply`
			`</name>`
			`<command>`
Now the test servers and test cases can run on a custom port number. There's no fixed port numbers in use anymore. Starting now, the default ports the servers use are 8990 - 8993. There's no option to modify these yet, but changing the $base option in the top of the runtests.pl script. 2004-09-08 04:08:38 -04:00			`http://%HOSTIP:%HTTPPORT/158 -F name=daniel`
getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 10:27:54 -04:00			`</command>`
			`</client>`

			`# Verify data after the test has been "shot"`
			`<verify>`
			`<strip>`
			`^Content-Type: multipart/form-data.*`
formpost: better random boundaries When doing multi-part formposts, libcurl used a pseudo-random value that was seeded with time(). This turns out to be bad for users who formpost data that is provided with users who then can guess how the boundary string will look like and then they can forge a different formpost part and trick the receiver. My advice to such implementors is (still even after this change) to not rely on the boundary strings being cryptographically strong. Fix your code and logic to not depend on them that much! I moved the Curl_rand() function into the sslgen.c source file now to be able to take advantage of the SSL library's random function if it provides one. If not, try to use the RANDOM_FILE for seeding and as a last resort keep the old logic, just modified to also add microseconds which makes it harder to properly guess the exact seed. The formboundary() function in formdata.c is now using 64 bit entropy for the boundary and therefore the string of dashes was reduced by 4 letters and there are 16 hex digits following it. The total length is thus still the same. Bug: http://curl.haxx.se/bug/view.cgi?id=1251 Reported-by: "Floris" 2013-06-24 16:24:35 -04:00			`^-----------------------.*`
getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 10:27:54 -04:00			`</strip>`
			`<protocol>`
			`POST /158 HTTP/1.1`
Replaced 127.0.0.1 with %HOSTIP where possible 2007-09-14 15:32:31 -04:00			`Host: %HOSTIP:%HTTPPORT`
runtests: provide curl's version string as %VERSION for tests ... so that we can check HTTP requests for User-Agent: curl/%VERSION Update 600+ test cases accordingly. Closes #6037 2020-10-02 07:45:24 -04:00			`User-Agent: curl/%VERSION`
getting only a 100 Continue response and nothing else, when talking HTTP, is now treated as an error by libcurl 2004-04-07 10:27:54 -04:00			`Accept: /`
			`Content-Length: 145`
			`Content-Type: multipart/form-data; boundary=----------------------------4f12fcdaa3bc`

			`------------------------------4f12fcdaa3bc`
			`Content-Disposition: form-data; name="name"`

			`daniel`
			`------------------------------4f12fcdaa3bc--`
			`</protocol>`
			`<errorcode>`
			`52`
			`</errorcode>`
			`</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. & => & ). 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>`