mirror of
https://github.com/moparisthebest/curl
synced 2024-12-23 08:38:49 -05:00
0dc4d8e42e
It does open up a miniscule risk that one of the other protocols that libcurl could use would send back a Content-Disposition header and then curl would act on it even if not HTTP. A future mitigation for this risk would be to allow the callback to ask libcurl which protocol is being used. Verified with test 1312 Closes #760
65 lines
929 B
Plaintext
65 lines
929 B
Plaintext
<testcase>
|
|
<info>
|
|
<keywords>
|
|
HTTP
|
|
HTTP GET
|
|
-J
|
|
</keywords>
|
|
</info>
|
|
|
|
#
|
|
<reply>
|
|
<data nocheck="yes">
|
|
HTTP/1.1 200 OK
|
|
Date: Thu, 09 Nov 2010 14:49:00 GMT
|
|
Server: test-server/fake
|
|
Content-Length: 6
|
|
Connection: close
|
|
Content-Type: text/html
|
|
Content-Disposition: inline; filename="name1312;weird"
|
|
|
|
12345
|
|
</data>
|
|
</reply>
|
|
|
|
#
|
|
# Client-side
|
|
<client>
|
|
# this relies on the debug feature to allow us to set directory to store the
|
|
# -J output in
|
|
<features>
|
|
debug
|
|
</features>
|
|
<server>
|
|
http
|
|
</server>
|
|
<name>
|
|
HTTP GET with -J, Content-Disposition and ; in filename
|
|
</name>
|
|
<setenv>
|
|
CURL_TESTDIR=%PWD/log
|
|
</setenv>
|
|
<command option="no-output,no-include">
|
|
%HOSTIP:%HTTPPORT/1312 -J -O
|
|
</command>
|
|
</client>
|
|
|
|
#
|
|
# Verify data after the test has been "shot"
|
|
<verify>
|
|
<strip>
|
|
^User-Agent:.*
|
|
</strip>
|
|
<protocol>
|
|
GET /1312 HTTP/1.1
|
|
Host: %HOSTIP:%HTTPPORT
|
|
Accept: */*
|
|
|
|
</protocol>
|
|
<file name="log/name1312;weird">
|
|
12345
|
|
</file>
|
|
|
|
</verify>
|
|
</testcase>
|