Age | Commit message (Collapse) | Author |
|
|
|
|
|
mailing list.
|
|
POSTing over HTTPS:// with NTLM works fine now. There was a general problem
with multi-pass authentication with non-GET operations with CONNECT.
|
|
|
|
|
|
enough. This is most likely the bug Jean-Louis Lemaire reported that makes
2GB FTP uploads to report error when completed.
Also padded comments to get them aligned again, only for visibility.
|
|
didn't properly check return code.
|
|
|
|
|
|
|
|
auth
|
|
server doesn't require any auth at all and then we just continue nicely. We
now have an extra bit in the connection struct named 'authprobe' that is TRUE
when doing pure "HTTP authentication probing".
|
|
anything newer than that
|
|
|
|
|
|
An attempt to repeat a reported auth problem. Works for me!
|
|
|
|
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.
|
|
|