| Age | Commit message (Collapse) | Author |
|---|
|
Add failure checking for servers when fork()ed.
Use same code path in 'stopserver' when called with a single or multiple pids.
|
|
when more than FD_SETSIZE file descriptors are open.
This means that if for any reason we are not able to
open more than FD_SETSIZE file descriptors then test
518 should not be run.
test 537 is all about testing libcurl functionality
when the system has nearly exhausted the number of
free file descriptors. Test 537 will try to run with
very few free file descriptors.
|
|
In this way we'll be able to sort out problems that might
arise in the prechek phase of the 518 test.
Once that 518 has been verified this change will be undone.
|
|
|
|
|
|
|
|
FTP 3rd party transfers to that file for now until I have them sorted out.
|
|
server as part of test cases
|
|
2 - store the time it took to verify it and allow that time to be used as
%FTPTIME[23] in command lines to allow us to adjust better to slow hosts
since test 190 failed on my slow solaris machine just because it hadn't
gotten time to run all the way the test assumed all machines would reach
before the time-out elapsed.
|
|
seconds even when everything is fine! Now we allow a test server 8 seconds
to respond to still be considered ok.
|
|
and it should break most other systems. The "funny" part is that debian
actually have a 'stunnel' setup to simulate stunnel v3 but it breaks our own
stunnel-version-detect-and-adjust-to-it system.
Added initial support for optionally running servers with fork support.
|
|
accordingly.
|
|
not supporting it. It hasn't been functioning for years anyway, so this is
just finally stating what already was true. And a cleanup at the same time.
|
|
test script to kill all processes in the current process group!
|
|
|
|
|
|
version.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
to the docs.
|
|
or the test is skipped. Ideally, we should let this test case go over a few
frequently used IPv6 localhost aliases...
|
|
|
|
download a file from the server before the server is considered fine to use
for the given test case. This should fix the cases where the server can run
but curl cannot work with it.
|
|
|
|
start... Anyway, fork() + exec() makes _two_ pids (in perl) that we need to
track and kill after use. Thankyouverymuch.
|
|
Made the ftp server use the passed in pidfile name, and made runtests.pl
pass it in properly.
|
|
a pidfile for the server appears as otherwise it failed.
|
|
|
|
|
|
and fixed the textmode attribute thing for windows a bit
|
|
|
|
|
|
sometimes the server can start but curl cannot speak to it, and then we must
remember the server (in order to kill it properly) anyway.
Also, make sure to kill all servers on exit everywhere.
|
|
|
|
(problem identified by Dan F)
2. initial text mode fix for file checks, to allow better text file testing
on windows (with regard to line endings)
3. fixed to use the proper ftpserver pidfile to find pid
|
|
|
|
|
|
"remaining: [time]" outputs to hint users about what to expect
|
|
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.
|
|
update the docs accordingly
|
|
|
|
is no longer only present when built with SSL support.
|
|
between platforms
|
|
server
|
|
test it outside the test suite. Now we also disable valgrind usage if libcurl
was built shared, as then valgrind is only testing the wrapper-script running
shell which is pointless.
|
|
previously didn't detect and report the "Conditional jump or move depends on
uninitialised value(s)" error.
When I fixed this, I caught a few curl bugs with it. And then I had to spend
time to make the test suite IGNORE these errors when OpenSSL is used since it
produce massive amounts of valgrind warnings (but only of the "Conditional..."
kind it seems).
So, if a test that requires SSL is run, it ignores the "Conditional..."
errors, and you'll get a "valgrind PARTIAL" output instead of "valgrind OK".
|
