← Back to branch summary

~ubuntu-branches/ubuntu/vivid/curl/vivid

« back to all changes in this revision

Viewing changes to tests/data/test1086

  • Committer: Bazaar Package Importer
  • Author(s): Andreas Schuldei
  • Date: 2009-04-02 23:35:45 UTC
  • mfrom: (1.1.12 upstream)
  • mto: (3.3.1 squeeze)
  • mto: This revision was merged to the branch mainline in revision 38.
  • Revision ID: james.westby@ubuntu.com-20090402233545-8xjr3o2sgce5s4bg
Tags: 7.19.4-1
http://bugs.debian.org/517277
* New upstream release
* Fix "newer bdb version" <explain what you changed and why> 
  (Closes: #517277)
* resolve libtool version confusion, thanks to 
  Stefanos Harhalakis <v13@v13.gr>
* add new dependency on libgcrypt11-dev due to newly arising binary symbols

Show diffs side-by-side

added added

removed removed

Lines of Context:
tests/data/test1086
 
1
<testcase>
 
2
<info>
 
3
<keywords>
 
4
FTP
 
5
EPSV
 
6
RETR
 
7
timeout
 
8
FAILURE
 
9
</keywords>
 
10
</info>
 
11
 
 
12
# Server-side
 
13
<reply>
 
14
# Overload some standard FTP responses to make them shorter and faster
 
15
# to avoid wasting time waiting for the data phase to start
 
16
<servercmd>
 
17
SLOWDOWN
 
18
REPLY USER 331 OK
 
19
REPLY PASS 230 OK
 
20
REPLY PWD 257 "/"
 
21
REPLY TYPE 200 OK
 
22
</servercmd>
 
23
<data nocheck="yes">
 
24
Long chunk of data that couldn't possibly be sent in the time allotted.
 
25
Long chunk of data that couldn't possibly be sent in the time allotted.
 
26
Long chunk of data that couldn't possibly be sent in the time allotted.
 
27
Long chunk of data that couldn't possibly be sent in the time allotted.
 
28
Long chunk of data that couldn't possibly be sent in the time allotted.
 
29
Long chunk of data that couldn't possibly be sent in the time allotted.
 
30
Long chunk of data that couldn't possibly be sent in the time allotted.
 
31
Long chunk of data that couldn't possibly be sent in the time allotted.
 
32
Long chunk of data that couldn't possibly be sent in the time allotted.
 
33
Long chunk of data that couldn't possibly be sent in the time allotted.
 
34
Long chunk of data that couldn't possibly be sent in the time allotted.
 
35
Long chunk of data that couldn't possibly be sent in the time allotted.
 
36
Long chunk of data that couldn't possibly be sent in the time allotted.
 
37
Long chunk of data that couldn't possibly be sent in the time allotted.
 
38
Long chunk of data that couldn't possibly be sent in the time allotted.
 
39
Long chunk of data that couldn't possibly be sent in the time allotted.
 
40
Long chunk of data that couldn't possibly be sent in the time allotted.
 
41
Long chunk of data that couldn't possibly be sent in the time allotted.
 
42
Long chunk of data that couldn't possibly be sent in the time allotted.
 
43
Long chunk of data that couldn't possibly be sent in the time allotted.
 
44
Long chunk of data that couldn't possibly be sent in the time allotted.
 
45
Long chunk of data that couldn't possibly be sent in the time allotted.
 
46
Long chunk of data that couldn't possibly be sent in the time allotted.
 
47
Long chunk of data that couldn't possibly be sent in the time allotted.
 
48
</data>
 
49
</reply>
 
50
 
 
51
# Client-side
 
52
<client>
 
53
<server>
 
54
ftp
 
55
</server>
 
56
<killserver>
 
57
ftp
 
58
</killserver>
 
59
 <name>
 
60
FTP download with strict timeout and slow data transfer
 
61
 </name>
 
62
 <command timeout="1">
 
63
ftp://%HOSTIP:%FTPPORT/1086 -m 6
 
64
</command>
 
65
</client>
 
66
 
 
67
# Verify data after the test has been "shot"
 
68
<verify>
 
69
# 28 is CURLE_OPERATION_TIMEDOUT
 
70
<errorcode>
 
71
28
 
72
</errorcode>
 
73
<protocol>
 
74
USER anonymous
 
75
PASS ftp@example.com
 
76
PWD
 
77
EPSV
 
78
TYPE I
 
79
SIZE 1086
 
80
RETR 1086
 
81
</protocol>
 
82
</verify>
 
83
</testcase>