| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
retrying upon EINTR errors.
|
|
the left side of @ to make it short(er).
|
|
SSL/TLS layer. http://www.mozilla.org/projects/security/pki/nss/
|
|
list of source files for those tests that use it. Otherwise testutil.h
might not be found by the compiler.
|
|
part of the official libcurl API http://curl.haxx.se/lxr/source/lib/README.curlx
The documented way of using them would be to use timeval.c as a source code file.
The above described method works very well when statically linking libcurl and
apps, test programs, but has several drawbacks when you build a true shared
libcurl (i.e. Name space clash at linkage stage as functions are defined more
than once. Windows makefiles are not capable of handling this system of
source-level sharing)
So...
Now testutil.h and testutil.c define and implement tutil_tvnow and tutil_tvdiff
which replace curlx_tvnow and curlx_tvdiff for the libtest programs. Doing this
we avoid the above described problems, and the code in the testsuite does not
impose the need to keep those functions public in libcurl even when not part of
the API.
|
|
part of the official libcurl API http://curl.haxx.se/lxr/source/lib/README.curlx
The documented way of using them would be to use timeval.c as a source code file.
The above described method works very well when statically linking libcurl and
apps, test programs, but has several drawbacks when you build a true shared
libcurl (i.e. Name space clash at linkage stage as functions are defined more
than once. Windows makefiles are not capable of handling this system of
source-level sharing)
So...
Now testutil.h and testutil.c define and implement tutil_tvnow and tutil_tvdiff
which replace curlx_tvnow and curlx_tvdiff for the libtest programs. Doing this
we avoid the above described problems, and the code in the testsuite does not
impose the need to keep those functions public in libcurl even when not part of
the API.
|
|
So cookie expiration date is lowered to expire at most in 2035.
|
|
|
|
|
|
|
|
jar has died and we now instead point out our own version of that
|
|
|
|
|
|
Next time in 2038 :-)
|
|
open file descriptors is greater than FD_SETSIZE minus SAFETY_MARGIN,
also skip the test if any of the open file descriptors has a number
greater than FD_SETSIZE minus SAFETY_MARGIN.
|
|
|
|
of poll() and select() happens to be bound by FD_SETSIZE
|
|
timval.c dependency on some of those
|
|
|
|
lib/timeval.c source code since those functions are not in the API (and might
not be accessible)
|
|
header, you got _two_ User-Agent headers in the CONNECT request...! Added
test case 287 to verify the fix.
|
|
|
|
|
|
|
|
variable from being properly used in many cases (and caused test case 63
to fail).
|
|
|
|
are not, due mainly to the lack of support for XML character entities
(e.g. & => & ). This will make it easier to validate test files using
tools like xmllint, as well as edit and view them using XML tools.
|
|
Check for the .exe extension on mingw32 builds.
|
|
|
|
|
|
|
|
|
|
|
|
Flush the protocol log data so it's immediately available to the test harness.
|
|
|
|
|
|
function(s) using SessionHandle pointers
|
|
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.
|
|
|
|
responded with a single status line and no headers nor body. Starting now, a
HTTP response on a persistent connection (i.e not set to be closed after the
response has been taken care of) must have Content-Length or chunked
encoding set, or libcurl will simply assume that there is no body.
To my horror I learned that we had no less than 57(!) test cases that did bad
HTTP responses like this, and even the test http server (sws) responded badly
when queried by the test system if it is the test system. So although the
actual fix for the problem was tiny, going through all the newly failing test
cases got really painful and boring.
|
|
This is done to back out changes done in revisions 1.77 and 1.75
|
|
This is done to back out changes done from revisions 1.213 to 1.217
|
|
This is done to back out changes done from revisions 1.6 to 1.10
|
|
|
|
|
|
have proper TERM and INT signal handlers implemented.
|
|
|
