Age | Commit message (Collapse) | Author |
|
The chunked transfer upload never stopped due to a silly add before we checked
for >0!
|
|
We now check if the chunked transfer-encoding header has been added "by force"
and if so, we enabled the chunky upload!
|
|
|
|
with --disable-ipv6 --without-zlib
|
|
|
|
FOLLOWLOCATION and CURLOPT_USERPWD.
|
|
|
|
for freeing single dns cache entries
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
for storage and retrieval of private data in the curl handle.
|
|
is not a good thing, as recent gccs for example complain if it is /usr/include
Right now, we just output "" until we think of something better.
|
|
|
|
CURLE_OPERATION_TIMEOUTED
|
|
|
|
|
|
|
|
|
|
|
|
|
|
until the pointers are set to another value
|
|
|
|
|
|
|
|
|
|
ConnectBits where the other bools already are
|
|
AGGRESIVE_TEST is also defined, as an addition to MALLOCDEBUG. It doesn't
work for multi interface usage and should only be used with careful
consideration.
|
|
|
|
should be removed soonish.
|
|
|
|
|
|
|
|
|
|
size of the uploaded file is unknown.
|
|
CURLOPT_CONNECTTIMEOUT was used and provided a fix.
|
|
|
|
|
|
|
|
debug wasn't enabled
|
|
|
|
counter so that the caller needs to decrease that counter when done with
the returned data.
If compiled with MALLOCDEBUG I've added some extra checking that the counter
is decreased before a handle is closed etc.
|
|
|
|
memory. Avery Fay brought the example code that proved this.
|
|
|