curl/tests/data/test538, branch master cURL mirror with patches applied multi tests: OOM handling fixes 2011-10-21T14:52:14+00:00 Yang Tse yangsita@gmail.com 2011-10-21T14:26:18+00:00 629d2e34508838069db83e1082ce9e7f2c7b8ff8 Additionally, improved error checking and logging. 
Additionally, improved error checking and logging.
Added multi keyword 2008-08-26T20:21:59+00:00 Dan Fandrich dan@coneharvesters.com 2008-08-26T20:21:59+00:00 fc09d10560fe3b43a652be5a278fa61f67fcfdd7 






Various test file cleanups, including using <servercmd> instead of writing
2007-04-18T20:22:01+00:00

Dan Fandrich
dan@coneharvesters.com

2007-04-18T20:22:01+00:00

ae3d5949b8611fd21d5397608bfd34d675156fad

directly to ftpserver.cmd and removing unneeded empty sections.





directly to ftpserver.cmd and removing unneeded empty sections.







ftp@example.com is now the new anonymous FTP password. I opted for 'ftp' on
2007-02-13T22:50:16+00:00

Daniel Stenberg
daniel@haxx.se

2007-02-13T22:50:16+00:00

4efa0d9f6800b12e3ecb7e0291bc80fa8d8aa610

the left side of @ to make it short(er).





the left side of @ to make it short(er).







Convert (most of) the test data files into genuine XML.  A handful still
2007-01-23T02:25:56+00:00

Dan Fandrich
dan@coneharvesters.com

2007-01-23T02:25:56+00:00

33bea767ebd0bbf11867fe1af31dc345e9f816af

are not, due mainly to the lack of support for XML character entities
(e.g. & => &amp; ).  This will make it easier to validate test files using
tools like xmllint, as well as edit and view them using XML tools.





are not, due mainly to the lack of support for XML character entities
(e.g. & => &amp; ).  This will make it easier to validate test files using
tools like xmllint, as well as edit and view them using XML tools.







Alexey Simak found out that when doing FTP with the multi interface and
2006-12-11T09:32:58+00:00

Daniel Stenberg
daniel@haxx.se

2006-12-11T09:32:58+00:00

88c8d72a214864952b6d1c2347b6c3f5b7d69e84

something went wrong like it got a bad response code back from the server,
libcurl would leak memory. Added test case 538 to verify the fix.

I also noted that the connection would get cached in that case, which
doesn't make sense since it cannot be re-use when the authentication has
failed. I fixed that issue too at the same time, and also that the path
would be "remembered" in vain for cases where the connection was about to
get closed.





something went wrong like it got a bad response code back from the server,
libcurl would leak memory. Added test case 538 to verify the fix.

I also noted that the connection would get cached in that case, which
doesn't make sense since it cannot be re-use when the authentication has
failed. I fixed that issue too at the same time, and also that the path
would be "remembered" in vain for cases where the connection was about to
get closed.