- Dec 27, 2014
-
-
Steve Holme authored
-
Steve Holme authored
This frees up the 'result' variable for CURLcode based result codes.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
...and don't use CURLE_OK in failure/success comparisons.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
As this feature has been implemented for 7.40.0.
-
Steve Holme authored
...as calloc() automatically clears the area of memory with zeros.
-
Steve Holme authored
...with the exception of the start of block statement curly brackets.
-
Steve Holme authored
For consistency, as we seem to have a bit of a mixed bag, changed all instances of ipv4 and ipv6 in comments and documentations to use the correct case.
-
Steve Holme authored
...following change in curl --version output.
-
- Dec 26, 2014
-
-
Steve Holme authored
Use Unix when generically writing about Unix based systems as UNIX is the trademark and should only be used in a particular product's name.
-
Steve Holme authored
if2ip.c:119: warning: unused parameter 'remote_scope_id' ...and some minor code style policing in the same function.
-
Steve Holme authored
Otherwise Curl_ssl_init_certinfo() can fail and set the num_of_certs member variable to the requested count, which could then be used incorrectly as libcurl closes down.
-
Steve Holme authored
The return type for this function was 0 on success and 1 on error. This was then examined by the calling functions and, in most cases, used to return CURLE_OUT_OF_MEMORY. Instead use CURLcode for the return type and return the out of memory error directly, propagating it up the call stack.
-
Steve Holme authored
To match the curl --version output.
-
Marc Hoersken authored
Merge multiple internal arrays into one, even if some variables will not not be used. They are all created with the number of file descriptors as their size. Also fix possible thread handle leak in CloseHandle-loop.
-
Marc Hoersken authored
Improves performance of test cases 574 and 575 by 50%. A value of zero causes the thread to relinquish the remainder of its time slice to any other thread of equal priority that is ready to run. If there are no other threads of equal priority ready to run, the function returns immediately, and the thread continues execution. http://msdn.microsoft.com/library/windows/desktop/ms686307.aspx
-
- Dec 25, 2014
-
-
Steve Holme authored
In line with the other features listed in the --version output, capitalise the UNIX socket feature.
-
Steve Holme authored
The return type of this function is a boolean value, and even uses a bool internally, so use bool in the function declaration as well as the variables that store the return value, to avoid any confusion.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
- Dec 24, 2014
-
-
Steve Holme authored
curl_ntlm_core.c:301: warning: pointer targets in passing argument 2 of 'CryptImportKey' differ in signedness curl_ntlm_core.c:310: warning: passing argument 6 of 'CryptEncrypt' from incompatible pointer type curl_ntlm_core.c:540: warning: passing argument 4 of 'CryptGetHashParam' from incompatible pointer type
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
Renamed ldap_setup() to ldap_setup_connection() to follow more widely used function naming.
-
Steve Holme authored
Renamed rtmp_setup() to rtmp_setup_connection() to follow more widely used function naming.
-
Steve Holme authored
Renamed smb_setup() to smb_setup_connection() to follow more widely used function naming.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
As this pre-processor definition is defined in curl_setup.h there is no need to include it in the Visual Studio project files.
-
Steve Holme authored
Removed the WIN64 pre-processor definition from the libcurl project files as: * WIN64 is not used in our source code * The curl projects files don't define it * It isn't required by or used in the platform SDK * For backwards compatability curl_setup.h defines WIN32 * The compiler automatically defines _WIN64 for x64 builds Historically Visual Studio projects have defined WIN32, in addition to the compiler defined _WIN32 definition, and I had incorrectly changed that to WIN64 for the x64 libcurl builds but not in the curl projects. As such, it is questionable whether this should be defined or not. For more information see the following cache of a discussion that took place on the microsoft.public.vc.mfc newsgroup: http://www.tech-archive.net/Archive/VC/microsoft.public.vc.mfc/2008-06/msg00074.html
-
- Dec 23, 2014
-
-
Steve Holme authored
openssl.c:1408: error: 'TLS1_1_VERSION' undeclared openssl.c:1411: error: 'TLS1_2_VERSION' undeclared
-
- Dec 22, 2014
-
-
John Malmberg authored
packages/vms/backup_gnv_curl_src.com: Originally copied from Bash port.
-
Daniel Stenberg authored
To offer some more info and yet it doesn't use more lines.
-