| Age | Commit message (Collapse) | Author |
|---|
|
to automatically uncompress it with the CURLOPT_ENCODING option, libcurl
could wrongly provide the callback with more data than what the maximum
documented amount. An application could thus get tricked into badness if the
maximum limit was trusted to be enforced by libcurl itself (as it is
documented).
This is further detailed and explained in the libcurl security advisory
20100209 at
http://curl.haxx.se/docs/adv_20100209.html
|
|
|
|
|
|
|
|
- cleanup parenthesis usage in return statements
|
|
|
|
|
|
|
|
Makefile.inc since that can't be included directly.
|
|
|
|
|
|
possible loss of data
|
|
|
|
initialized.
|
|
possible loss of data
|
|
Simplify preprocessor symbol checking
|
|
slightly while editing
|
|
writing out the whole header. The docs say it writes the whole header,
but the code (before this patch) did not write out the leading $.
|
|
simply check for CURLM_CALL_MULTI_PERFORM internally. This has the added
benefit that this goes in line with my long-term wishes to get rid of the
CURLM_CALL_MULTI_PERFORM all together from the public API.
|
|
string buffer, otherwise Curl_client_write() call with zero size would write
to the end of string buffer including matched POP3_EOB.
|
|
|
|
|
|
check for (excess > 0 && !k->ignorebody).
|
|
|
|
|
|
|
|
|
|
proxy that cannot be resolved when using c-ares. This matches the behaviour
when not using c-ares.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from hostip.h to setup.h in order to allow proper inclusion in any file.
This represents no functional change at all in which resolver is used,
everything still works as usual, internally and externally there is no
difference in behavior.
|
|
|
|
|
|
|
|
systems
|
|
|
|
|
|
s/RTPDATA/INTERLEAVEDATA/
|
