aboutsummaryrefslogtreecommitdiff
path: root/lib/README.memoryleak
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2008-04-05 21:02:38 +0000
committerDaniel Stenberg <daniel@haxx.se>2008-04-05 21:02:38 +0000
commit7607d5145bbacd76d45bca405edc12f4b613418c (patch)
treeea3ecf643bfa3b2a0396a7040b3ffd62e5037770 /lib/README.memoryleak
parent12a90289ed7e600a997fde9448a0128b590f1f3d (diff)
- Based on the Debian bug report #474224 that complained about the FTP error
message when libcurl doesn't get a 220 back immediately on connect, I now changed it to be more specific on what the problem is. Also worth noticing: while the bug report contains an example where the response is: 421 There are too many connected users, please try again later we cannot assume that the error message will always be this readable nor that it fits within a particular boundary etc.
Diffstat (limited to 'lib/README.memoryleak')
0 files changed, 0 insertions, 0 deletions