- Doesn't allow you to disable specific protocols from the build
- Doesn't find or use krb4 or GSS
- Rebuilds test files too eagerly, but still can't run the tests
- - Does't detect the correct strerror_r flavor when cross-compiling (issue #1123)
+ - Doesn't detect the correct strerror_r flavor when cross-compiling (issue #1123)
Command Line CMake
You can specify the private and public keys for SSH/SSL as file paths. Some
programs want to avoid using files and instead just pass them as in-memory
data blobs. There's probably a challenge to make this work across the
- plethory of different TLS and SSH backends that curl suppports.
+ plethory of different TLS and SSH backends that curl supports.
https://github.com/curl/curl/issues/2310
13.4 Cache/share OpenSSL contexts
/* This is an application verification call back, it does not
perform any addition verification but tries to find a URL
- in the presented certificat. If found, this will become
+ in the presented certificate. If found, this will become
the URL to be used in the POST.
*/
*
***************************************************************************/
/* <DESC>
- * Connection cache shared between easy handles with the share inteface
+ * Connection cache shared between easy handles with the share interface
* </DESC>
*/
#include <stdio.h>
This value used to be fairly big (100K), but we must take into account that
if the server rejects the POST due for authentication reasons, this data
- will always be uncondtionally sent and thus it may not be larger than can
+ will always be unconditionally sent and thus it may not be larger than can
always be afforded to send twice.
It must not be greater than 64K to work on VMS.
}
}
- /* Initilise the security context and decode our challenge */
+ /* Initialize the security context and decode our challenge */
result = Curl_auth_decode_spnego_message(data, userp, passwdp, service,
host, header, neg_ctx);
static char *Curl_basename(char *path)
{
/* Ignore all the details above for now and make a quick and simple
- implementaion here */
+ implementation here */
char *s1;
char *s2;
well be the same we read from.
CURL_SOCKET_BAD disables */
- /** Dynamicly allocated strings, MUST be freed before this **/
+ /** Dynamically allocated strings, MUST be freed before this **/
/** struct is killed. **/
struct dynamically_allocated_data {
char *proxyuserpwd;
#endif /* CURL_BUILD_MAC */
#if CURL_BUILD_MAC_10_8 || CURL_BUILD_IOS
- if(SSLCreateContext != NULL) { /* use the newer API if avaialble */
+ if(SSLCreateContext != NULL) { /* use the newer API if available */
if(BACKEND->ssl_ctx)
CFRelease(BACKEND->ssl_ctx);
BACKEND->ssl_ctx = SSLCreateContext(NULL, kSSLClientSide, kSSLStreamType);
'make djgpp' in the root curl dir should build it fine.
Note 1: djgpp 2.04 beta has a sscanf() bug so the URL parsing isn't
- done proberly. Use djgpp 2.03 until they fix it.
+ done properly. Use djgpp 2.03 until they fix it.
Note 2: Compile Watt-32 (and OpenSSL) with the same version of djgpp.
Otherwise things go wrong because things like FS-extensions and
{
PK11Context *ctx;
- /* we have to initialize NSS if not initialized alraedy */
+ /* we have to initialize NSS if not initialized already */
if(!NSS_IsInitialized() && !nss_context) {
static NSSInitParameters params;
params.length = sizeof params;
size_t count = 0;
struct OperationConfig *operation = config->first;
- /* Get the required aguments for each operation */
+ /* Get the required arguments for each operation */
while(!result && operation) {
result = get_args(operation, count++);
<reply>
<servercmd>
-REPLY PRET 550 unkown command
+REPLY PRET 550 unknown command
</servercmd>
</reply>
# The protocol part does not include QUIT simply because the error is
# CURLE_OPERATION_TIMEDOUT (28) which is a generic timeout error without
-# specificly saying for which connection it concerns, and for timeouts libcurl
+# specifically saying for which connection it concerns, and for timeouts libcurl
# marks the control channel as "invalid". As this test case times out for the
# data connection it could still use the control channel.
<protocol>
# This is supposed to be returned when the server gets the second
# Authorization: NTLM line passed-in from the client
<data1002>
-HTTP/1.1 200 Type-3 Recevied and all Things are fine swsclose\r
+HTTP/1.1 200 Type-3 Received and all Things are fine swsclose\r
Server: Microsoft-IIS/5.0\r
Content-Type: text/html; charset=iso-8859-1\r
Content-Length: 32\r
Content-Type: text/html; charset=iso-8859-1\r
WWW-Authenticate: NTLM TlRMTVNTUAACAAAAAgACADAAAAAGgoEAc51AYVDgyNcAAAAAAAAAAG4AbgAyAAAAQ0MCAAQAQwBDAAEAEgBFAEwASQBTAEEAQgBFAFQASAAEABgAYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAwAsAGUAbABpAHMAYQBiAGUAdABoAC4AYwBjAC4AaQBjAGUAZABlAHYALgBuAHUAAAAAAA==\r
\r
-HTTP/1.1 200 Type-3 Recevied and all Things are fine swsclose\r
+HTTP/1.1 200 Type-3 Received and all Things are fine swsclose\r
Server: Microsoft-IIS/5.0\r
Content-Type: text/html; charset=iso-8859-1\r
Content-Length: 32\r
# at a regular interval. The output is suitable to be mailed to
# curl-autocompile@haxx.se to be dealt with automatically (make sure the
# subject includes the word "autobuild" as the mail gets silently discarded
-# otherwise). The most current build status (with a resonable backlog) will
+# otherwise). The most current build status (with a reasonable backlog) will
# be published on the curl site, at https://curl.haxx.se/auto/
# USAGE:
projects / thirdparty / curl.git / commitdiff
