| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
and avoid using ! as last char of line.
|
|
before resorting to the kill -9 hammer.
Added test harness infrastructure to support scp/sftp tests, using
OpenSSH as the server.
|
|
since that is the API yassl attempts to provide
|
|
'crypto' tests aren't dependent on SSL. Compiling with
--disable-crypto-auth will cause test failures, however.
|
|
appropriate test case to use it. For now, this is treated the same as the
"SSL" feature because curl doesn't list it separately.
|
|
test, fixing KNOWN_BUGS #11. Fixed some tests to more accurately specify
their required servers and features.
|
|
supports only ftps:// URLs with --ftp-ssl-control specified, which
implicitly encrypts the control channel but not the data channels. That
allows stunnel to be used with an unmodified ftp server in exactly the
same way that the test https server is set up.
Added test case 400 as a basic FTPS test.
|
|
|
|
SSL/TLS layer. http://www.mozilla.org/projects/security/pki/nss/
|
|
|
|
variable from being properly used in many cases (and caused test case 63
to fail).
|
|
|
|
This is done to back out changes done from revisions 1.213 to 1.217
|
|
|
|
|
|
servers hash, and adjust message arguments accordingly.
|
|
|
|
server holds not only its two main pids, but also the pidfile of the test
server and the 'slavepidfiles' for ftp* servers. This allows a better control
when stopping servers.
Now from runtests.pl when test servers are stopped they are signalled in
sequence TERM, INT and KILL allowing time in between for them to die. This
will give us a chance of gracefully stopping test servers, which we didn't
have when we were killing them in first instance.
|
|
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.
|
