| Age | Commit message (Collapse) | Author |
|---|
|
file until it is actually being uploaded.
Make sure we build and still work with HTTP disabled - the SSL code might use
the boundary string for some random seeding.
|
|
|
|
might be used uninitialized
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a host name that resolves to multiple IP addresses.
|
|
|
|
path after a transfer.
|
|
--disable-http, which thus builds a libcurl without HTTP support.
|
|
keep the API complete at all times
|
|
|
|
|
|
Setting CURLOPT_RESUME_FROM to 0 prevents a resumed transfer.
|
|
|
|
An Alexander Krasnostavsky fix.
|
|
|
|
|
|
if one transfer fails.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
marked as accepting an objectpoint argument while it actually assumes a long.
The comment was also grossly misleading. The man page was and is correct
though.
|
|
|
|
|
|
work. This is supposed to detect cross-compiling and alert the user, and not
do the POSIX-check for strerror_r() if it already detected a glibc-compatible
strerror_r().
|
|
to/from, based on a suggestion from Alexander Krasnostavsky
|
|
|
|
the user.
2 - don't check for POSIX-style if glibc-style is found first
|
