1
0
mirror of https://github.com/moparisthebest/curl synced 2024-12-21 15:48:49 -05:00

Each test case now specifies which server(s) it needs, without relying on the

test number.
This commit is contained in:
Daniel Stenberg 2003-04-30 20:25:39 +00:00
parent 15f3f4c93f
commit ee29dbdb8f
114 changed files with 342 additions and 0 deletions

View File

@ -20,6 +20,9 @@ Funny-head: yesyes
#
# Client-side
<client>
<server>
http
</server>
<name>
simple HTTP GET
</name>

View File

@ -12,6 +12,9 @@ blablabla
# Client-side
<client>
<server>
http
</server>
<name>
simple HTTP PUT from file
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP dir list PASV
</name>

View File

@ -17,6 +17,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP dir list, PORT with specified IP
</name>

View File

@ -12,6 +12,9 @@ works
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP RETR PASV
</name>

View File

@ -12,6 +12,9 @@ works
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP RETR PORT with CWD
</name>

View File

@ -7,6 +7,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP --head to get file size only
</name>

View File

@ -12,6 +12,9 @@ works
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP user+password in URL and ASCII transfer
</name>

View File

@ -12,6 +12,9 @@ works
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP GET with type=A style ASCII URL using %20 codes
</name>

View File

@ -1,6 +1,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP PASV upload file
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP PORT upload with CWD
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP PASV upload append
</name>

View File

@ -36,6 +36,9 @@ If this is received, the location following worked
# Client-side
<client>
<server>
http
</server>
<name>
simple HTTP Location: following
</name>

View File

@ -11,6 +11,9 @@ but we emulate that
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download resume with set limit
</name>

View File

@ -7,6 +7,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download resume beyond file size
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP PASV upload resume
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed login: USER not valid
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed login: PASS not valid
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed PASV
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed PORT
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed TYPE
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed RETR
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed RETR with PORT
</name>

View File

@ -20,6 +20,9 @@ ink="#ffffff" vlink="#cccccc">
# Client-side
<client>
<server>
http
</server>
<name>
HTTP range support
</name>

View File

@ -12,6 +12,9 @@ works
# Client-side
<client>
<server>
ftp
</server>
<name>
ftp download with post-quote delete operation
</name>

View File

@ -12,6 +12,9 @@ works
# Client-side
<client>
<server>
ftp
</server>
<name>
ftp download with post- and pre-transfer delete operations
</name>

View File

@ -7,6 +7,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download resume with whole file already downloaded
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP upload resume with whole file already downloaded
</name>

View File

@ -7,6 +7,9 @@ we can still send data even if pwd fails!
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed PWD
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download, failed CWD
</name>

View File

@ -7,6 +7,9 @@ this is file contents
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download with multiple replies at once in RETR
</name>

View File

@ -7,6 +7,9 @@ moooooooo
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP --disable-epsv
</name>

View File

@ -4,6 +4,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP upload with --crlf
</name>

View File

@ -11,6 +11,9 @@ blabla custom request result
# Client-side
<client>
<server>
http
</server>
<name>
HTTP custom request 'DELETE'
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client requires=netrc_debug>
<server>
ftp
</server>
<name>
FTP (optional .netrc; no user/pass) dir list PASV
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client requires=netrc_debug>
<server>
ftp
</server>
<name>
FTP (optional .netrc; user/no pass) dir list PASV
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client requires=netrc_debug>
<server>
ftp
</server>
<name>
FTP (optional .netrc; user/passwd supplied) dir list PASV
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client requires=netrc_debug>
<server>
ftp
</server>
<name>
FTP (compulsory .netrc; ignored user/passwd) dir list PASV
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client requires=netrc_debug>
<server>
ftp
</server>
<name>
FTP (optional .netrc; programmatic user/passwd) dir list PASV
</name>

View File

@ -16,6 +16,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP retrieve a byte-range
</name>

View File

@ -7,6 +7,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP with user and no password
</name>

View File

@ -7,6 +7,9 @@ this is file contents
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download without size in RETR string
</name>

View File

@ -10,6 +10,9 @@ this is file contents
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download without size in RETR string and no SIZE command
</name>

View File

@ -10,6 +10,9 @@ this is file contents
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download a newer file with -z
</name>

View File

@ -10,6 +10,9 @@ Connection: close
# Client-side
<client>
<server>
http
</server>
<name>
HTTP HEAD with Connection: close
</name>

View File

@ -9,6 +9,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download file with -z, expected to not transfer
</name>

View File

@ -9,6 +9,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download info with -I
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP URL with too deep (100+) dir hierarchy
</name>

View File

@ -12,6 +12,9 @@ Repeated nonsense-headers
# Client-side
<client>
<server>
http
</server>
<name>
--write-out test
</name>

View File

@ -13,6 +13,9 @@ the content goes here
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with proxy athorization
</name>

View File

@ -10,6 +10,9 @@ This is the proof it works
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with config file on stdin
</name>

View File

@ -22,6 +22,9 @@ hoo
# Client-side
<client>
<server>
http
</server>
<name>
multiple requests using {} in URL
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
none
</server>
<name>
attempt connect to non-listening socket
</name>

View File

@ -5,6 +5,9 @@ moooooooo
# Client-side
<client>
<server>
ftp
</server>
<name>
FTP download with strict timeout and slow CWD
</name>

View File

@ -14,6 +14,9 @@ Funny-head: yesyes
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP GET with user and password
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
http
</server>
<name>
attempt connect to non-existing host name
</name>

View File

@ -11,6 +11,9 @@ moo
# Client-side
<client>
<server>
none
</server>
<name>
basic file:// file
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
none
</server>
<name>
missing file:// file
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
none
</server>
<name>
two file:// URLs to stdout
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
http
</server>
<name>
use curl with multiple request methods
</name>

View File

@ -10,6 +10,9 @@ This is the proof it works
# Client-side
<client>
<server>
http
</server>
<name>
get HTTP with URL > 10000 bytes
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
http
</server>
<name>
unsupported protocol:// URL
</name>

View File

@ -10,6 +10,9 @@ This silly page doesn't reaaaaaly exist so you should not get it.
# Client-side
<client>
<server>
http
</server>
<name>
HTTP GET fail silently on HTTP error return
</name>

View File

@ -51,6 +51,9 @@ Connection: close
# Client-side
<client>
<server>
http
</server>
<name>
looping HTTP Location: following with --max-redirs, no persistance
</name>

View File

@ -11,6 +11,9 @@ Connection: close
# Client-side
<client>
<server>
http
</server>
<name>
specify more -o than URLs
</name>

View File

@ -11,6 +11,9 @@ Set-Cookie: path=/; thewinneris=nowayyouwin;
# Client-side
<client>
<server>
http
</server>
<name>
Get same cookie page several times
</name>

View File

@ -36,6 +36,9 @@ If this is received, the location following worked
# Client-side
<client>
<server>
http
</server>
<name>
HTTP Location: following with extra spaces in header
</name>

View File

@ -14,6 +14,9 @@ wait 10
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with 2 secs timeout
</name>

View File

@ -14,6 +14,9 @@ this is data even though Content-Length is set to zero
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP POST with user and password
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with no data in server reply
</name>

View File

@ -14,6 +14,9 @@ MooMoo
#
# Client-side
<client>
<server>
https
</server>
<name>
simple HTTPS GET
</name>

View File

@ -14,6 +14,9 @@ Funny-head: yesyes
#
# Client-side
<client>
<server>
https
</server>
<name>
HTTPS GET with user and password
</name>

View File

@ -7,6 +7,9 @@ MOOOOO
#
# Client-side
<client>
<server>
https
</server>
<name>
HTTPS GET over HTTP proxy fails
</name>

View File

@ -14,6 +14,9 @@ wait 10
# Client-side
<client>
<server>
https
</server>
<name>
HTTPS with 2 secs timeout
</name>

View File

@ -12,6 +12,9 @@ blablabla
# Client-side
<client>
<server>
https
</server>
<name>
HTTPS multipart formpost
</name>

View File

@ -6,6 +6,9 @@
# Client-side
<client>
<server>
https
</server>
<name>
insecure HTTPS without permission
</name>

View File

@ -27,6 +27,9 @@ verify
#
# Client-side
<client>
<server>
https
</server>
<name>
HTTPS GET, receive no headers only data!
</name>

View File

@ -23,6 +23,9 @@ boo
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with weirdly formatted cookies and cookiejar storage
</name>

View File

@ -20,6 +20,9 @@ Funny-head: yesyes
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with -d and -G
</name>

View File

@ -7,6 +7,9 @@
# Client-side
<client>
<server>
http
</server>
<name>
HTTP PUT with resume
</name>

View File

@ -30,6 +30,9 @@ aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaabbbbbbbbbbbbbbbb
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP GET with chunked Transfer-Encoding
</name>

View File

@ -26,6 +26,9 @@ a
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP GET with bad chunked Transfer-Encoding
</name>

View File

@ -8,6 +8,9 @@
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP GET with nothing returned from server
</name>

View File

@ -12,6 +12,9 @@ todelooooo lalalala yada yada, we know nothing about ranges ;-)
# Client-side
<client>
<server>
http
</server>
<name>
HTTP resume request without server supporting it
</name>

View File

@ -12,6 +12,9 @@ blablabla
# Client-side
<client>
<server>
http
</server>
<name>
HTTP RFC1867-type formposting with filename= and type=
</name>

View File

@ -14,6 +14,9 @@ Funny-head: yesyes
#
# Client-side
<client>
<server>
http
</server>
<name>
Replaced internal and added custom HTTP headers
</name>

View File

@ -19,6 +19,9 @@ dr-xr-xr-x 5 0 1 512 Oct 1 1997 usr
#
# Client-side
<client>
<server>
ftps
</server>
<name>
FTPS dir list PASV
</name>

View File

@ -5,6 +5,9 @@ moooooooo
# Client-side
<client>
<server>
ftps
</server>
<name>
FTPS download with strict timeout and slow CWD
</name>

View File

@ -5,6 +5,9 @@ moooooooo
# Client-side
<client>
<server>
ftps
</server>
<killserver>
ftp
</killserver>

View File

@ -8,6 +8,9 @@
#
# Client-side
<client>
<server>
ftps
</server>
<name>
insecure FTPS without permission
</name>

View File

@ -36,6 +36,9 @@ If this is received, the location following worked
# Client-side
<client>
<server>
http
</server>
<name>
HTTP Location: following over HTTP proxy
</name>

View File

@ -12,6 +12,9 @@ blablabla
# Client-side
<client>
<server>
http
</server>
<name>
HTTP RFC1867-type formposting without Expect: header
</name>

View File

@ -36,6 +36,9 @@ If this is received, the location following worked
# Client-side
<client>
<server>
http
</server>
<name>
simple HTTP Location: without protocol in initial URL
</name>

View File

@ -17,6 +17,9 @@ This server reply is for testing a simple Location: following
# Client-side
<client>
<server>
http
</server>
<name>
HTTP, get cookies and store in cookie jar
</name>

View File

@ -13,6 +13,9 @@ Server: test-server/fake
#
# Client-side
<client>
<server>
http
</server>
<name>
simple HTTP 1.0 GET
</name>

View File

@ -12,6 +12,9 @@ Connection: close
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP with -d and -G and -I
</name>

View File

@ -34,6 +34,9 @@ body
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP follow redirect with ../
</name>

View File

@ -14,6 +14,9 @@ Funny-head: yesyes
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP over proxy
</name>

View File

@ -34,6 +34,9 @@ body
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP follow redirect with ../../
</name>

View File

@ -34,6 +34,9 @@ body
#
# Client-side
<client>
<server>
http
</server>
<name>
HTTP follow redirect with exessive ../
</name>

Some files were not shown because too many files have changed in this diff Show More