aboutsummaryrefslogtreecommitdiff
path: root/tests/data
AgeCommit message (Collapse)Author
2005-10-20Dave Dribin made libcurl understand and handle cases when the serverDaniel Stenberg
(wrongly) sends *two* WWW-Authenticate headers for Digest. While this should never happen in a sane world, libcurl previously got into an infinite loop when this occurred. Dave added test 273 to verify this.
2005-10-05added test case 272 for -z download over FTP when the timestamp is identicalDaniel Stenberg
to the remote one
2005-09-19added test 271Daniel Stenberg
2005-09-19test 271, the first ever TFTP testDaniel Stenberg
2005-09-04Added FTP_SKIP_PASV_IP and --ftp-skip-pasv-ipDaniel Stenberg
2005-08-24Toby Peterson added CURLOPT_IGNORE_CONTENT_LENGTH to the library, accessibleDaniel Stenberg
from the command line tool with --ignore-content-length. This will make it easier to download files from Apache 1.x (and similar) servers that are still having problems serving files larger than 2 or 4 GB. When this option is enabled, curl will simply have to wait for the server to close the connection to signal end of transfer. I wrote test case 269 that runs a simple test that this works.
2005-08-12added test 268 that makes curl -d @nonexistingDaniel Stenberg
2005-08-11do a POST with NTLM and add two custom headersDaniel Stenberg
2005-07-12Adrian Schuur added trailer support in the chunked encoding stream. TheDaniel Stenberg
trailer is then sent to the normal header callback/stream.
2005-07-03Andrew Bushnell provided enough info for me to tell that we badly needed toDaniel Stenberg
fix the CONNECT authentication code with multi-pass auth methods (such as NTLM) as it didn't previously properly ignore response-bodies - in fact it stopped reading after all response headers had been received. This could lead to libcurl sending the next request and reading the body from the first request as response to the second request. (I also renamed the function, which wasn't strictly necessary but...) The best fix would to once and for all make the CONNECT code use the ordinary request sending/receiving code, treating it as any ordinary request instead of the special-purpose function we have now. It should make it better for multi-interface too. And possibly lead to less code... Added test case 265 for this. It doesn't work as a _really_ good test case since the test proxy is too stupid, but the test case helps when running the debugger to verify.
2005-06-22verify that the URL decoding is done properly tooDaniel Stenberg
2005-06-22David Shaw's fix that unifies proxy string treatment so that a proxy givenDaniel Stenberg
with CURLOPT_PROXY can use a http:// prefix and user + password. The user and password fields are now also URL decoded properly. Test case 264 added to verify.
2005-06-03Andres Garcia's text mode fix for the 'data' partDaniel Stenberg
2005-05-31Todd Kulesza reported a flaw in the proxy option, since a numerical IPv6Daniel Stenberg
address was not possible to use. It is now, but requires it written RFC2732-style, within brackets - which incidently is how you enter numerical IPv6 addresses in URLs. Test case 263 added to verify.
2005-05-31added keywordsDaniel Stenberg
2005-05-29Eric Cooper reported about a problem with HTTP servers that responds withDaniel Stenberg
binary zeroes within the headers. They confused libcurl to do wrong so the downloaded headers become incomplete. The fix is now verified with test case 262.
2005-05-24Andres Garcia's mode=text patch to make these do fine on WindowsDaniel Stenberg
2005-05-24add test case 261, response code 226 to TYPEDaniel Stenberg
2005-05-21added keywordsDaniel Stenberg
2005-05-20keywords addedDaniel Stenberg
2005-05-20shorter nameDaniel Stenberg
2005-05-20Add support for text mode on stdout tests as well, and add the mode=textDaniel Stenberg
to the docs.
2005-05-18Bug report #1204435 identified a problem with malformed URLs likeDaniel Stenberg
"http://somehost?data" as it added a slash too much in the request ("GET /?data/"...). Added test case 260 to verify.
2005-05-17Made test case 241 precheck that the given name resolves to an ipv6 address,Daniel Stenberg
or the test is skipped. Ideally, we should let this test case go over a few frequently used IPv6 localhost aliases...
2005-05-11Modified the default HTTP headers used by libcurl:Daniel Stenberg
A) Normal non-proxy HTTP: - no more "Pragma: no-cache" (this only makes sense to proxies) B) Non-CONNECT HTTP request over proxy: - "Pragma: no-cache" is used (like before) - "Proxy-Connection: Keep-alive" (for older style 1.0-proxies) C) CONNECT HTTP request over proxy: - "Host: [name]:[port]" - "Proxy-Connection: Keep-alive"
2005-05-06Added two test cases for multipart formpost over a proxy with --anyauth. OurDaniel Stenberg
HTTP test server is a bit limited though, as it never responds to the POST request until all data has been sent (and received)...
2005-04-28Set mode text on the section that is written by curl in text mode, to allowDaniel Stenberg
the runtests.pl to check this differently on operating systems that differentiate on this.
2005-04-27keyword updateDaniel Stenberg
2005-04-25Fred New reported a bug where we used Basic auth and user name and password inDaniel Stenberg
.netrc, and when following a Location: the subsequent requests didn't properly use the auth as found in the netrc file. Added test case 257 to verify my fix.
2005-04-22keywords addedDaniel Stenberg
2005-04-22test 256 is like test 38 but with proxy + proxy authDaniel Stenberg
2005-04-22keywordsDaniel Stenberg
2005-04-19added CURLOPT_PORT test when using proxyDaniel Stenberg
2005-04-18Olivier reported that even though he used CURLOPT_PORT, libcurl clearly stillDaniel Stenberg
used the default port. He was right. I fixed the problem and added the test cases 521, 522 and 523 to verify the fix.
2005-04-18Toshiyuki Maezawa reported that when doing a POST with a read callback,Daniel Stenberg
libcurl didn't properly send an Expect: 100-continue header. It does now.
2005-04-18ARGH my stupidity is endless. Ipv4-only hosts don't send EPRT or LPRT.Daniel Stenberg
2005-04-18Modified the FTP server to use the new 'sockfilt' program to do all the socketDaniel Stenberg
level stuff. The FTP server communicates with sockfilt using perl's open2(). This enables easier IPv6 support and hopefully FTP-SSL support in the future. Added four test cases for FTP-ipv6.
2005-04-16keywords addedDaniel Stenberg
2005-04-16keywords addedDaniel Stenberg
2005-04-15started adding "keywords" for each test, to better allow us to sum up whatDaniel Stenberg
kind of tests we have and how many tests that test certain features
2005-04-14Two new slowdown tests for better testing of the FTP response reader functionDaniel Stenberg
when the response come in many small chunks.
2005-04-13fix port numberDaniel Stenberg
2005-04-12requires OpenSSL, as our GnuTLS doesn't provide support forDaniel Stenberg
CURLOPT_SSL_CTX_FUNCTION (yet).
2005-04-08fixed the 304 response-with-content-length problem reported by Cory NelsonDaniel Stenberg
2005-04-05test time-conditioned FTP uploadsDaniel Stenberg
2005-04-03Hardeep Singh reported a problem doing HTTP POST with Digest. (It was actuallyDaniel Stenberg
also affecting NTLM and Negotiate.) It turned out that if the server responded with 100 Continue before the initial 401 response, libcurl didn't take care of the response properly. Test case 245 and 246 added to verify this.
2005-04-03Test 245 was just added in an attempt to repeat Hardeep Singh's recent bug.Daniel Stenberg
But this works just fine on my host. Plain HTTP POST using Digest.
2005-03-28Based on Augustus Saunders' comments and findings, the HTTP output authDaniel Stenberg
function was fixed to use the proper proxy authentication when multiple ones were added as accepted. test 239 and test 243 were added to repeat the problems and verify the fixes.
2005-03-21Make NTLM tests depend on the NTLM feature at not SSL, since the NTLM supportDaniel Stenberg
is no longer only present when built with SSL support.
2005-03-17Change the bogus address used in test237 to be more reliable when runDan Fandrich
on a host with a buggy resolver that strips all but the bottom 8 bits of each octet. The resolved address in this case (192.0.2.127) is guaranteed never to belong to a real host (see RFC3330).