Age | Commit message (Collapse) | Author |
|
|
|
lingering POST-stuff that confuses GET requests. Juan F. Codagnone reported
this problem in bug report #653859.
|
|
header is used, we must wait for a 100-code (or timeout), before we send the
data. The timeout is merely 1000 ms at this point. We may have reason to set
a longer timeout in the future.
|
|
way for emacs, and vim users should provide a similar non-polluting style
|
|
|
|
regular transfer process. This required some new tweaks, like for example
we need to be able to tell the tranfer loop to not chunky-encode uploads
while we're transferring the rest of the request...
|
|
read callback, and thus won't put a lot of stress on the request sending
code (which currently does an ugly loop).
|
|
connectdata struct instead, and is no longer modified within the 'set' struct
as previously (which was a really BAAAD thing).
|
|
|
|
We now check if the chunked transfer-encoding header has been added "by force"
and if so, we enabled the chunky upload!
|
|
FOLLOWLOCATION and CURLOPT_USERPWD.
|
|
ConnectBits where the other bools already are
|
|
size of the uploaded file is unknown.
|
|
you set CURLOPT_PROXY to "".
|
|
memory as otherwise we (might) leak memory
|
|
|
|
case 306 added to verify that we do right
|
|
when talking to a IPv6-server using IPv6 IP address only.
|
|
|
|
|
|
working for "IPv6 enabled" libcurls yet, but should be pretty easy for
someone to adjust.
|
|
|
|
|
|
pointer. Bugs item #566835.
|
|
|
|
|
|
will then return CURLE_READ_ERROR.
|
|
|
|
CURLOPT_DEBUGFUNCTION and CURLOPT_DEBUGDATA.
|
|
|
|
|
|
we should read the POST-data from the read callback
|
|
|
|
|
|
was an extra CRLF added to the post data
|
|
|
|
pointed out this ugliness.
|
|
again. THIS IS NOT A NICE FIX.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
HTTP server we return error
|
|
|
|
libcurl should use in its request
|