- Feb 28, 2014
-
-
Daniel Stenberg authored
nghttp2 has yet again extended its callback struct and this is an attempt to make curl compile with nghttp2 from current git
-
Dan Fandrich authored
-
Steve Holme authored
-
- Feb 27, 2014
-
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
Other global options such as --libcurl, --trace and --verbose to follow.
-
Steve Holme authored
In order to ease the moving of global options such as the error stream, updated the OperationConfig structure to point to the GlobalConfig.
-
- Feb 26, 2014
-
-
Steve Holme authored
In addition to adding support for URL specific options via the command line with --next it is now possible to specify "next" in .curlrc.
-
Steve Holme authored
Follow up to commit 1a9b58fc to replace the : command line option with --next and -:.
-
Steve Holme authored
Added initial support for --next/-: which will be used to replace the rather confusing : command line operation what was used for the URL specific options prototype.
-
Dan Fandrich authored
A recent change seems to have slightly changed the call stack produced by the gcc optimizer.
-
- Feb 25, 2014
-
-
Nick Zitzmann authored
darwinssl: don't omit CN verification when an IP address is used
-
Daniel Stenberg authored
-
naota authored
Change "==" to "=" to honor POSIX test construction.
-
Steve Holme authored
...and added the HTTP suffix as these options are only used for HTTP2 based connections.
-
Steve Holme authored
Other global options such as --libcurl, --trace and --verbose to follow.
-
Steve Holme authored
In preparation for parsing global options added the GlobalConfig structure to the getparameter() function.
-
Steve Holme authored
warning: declaration of 'struct GlobalConfig' will not be visible outside of this function
-
- Feb 24, 2014
-
-
Marc Hoersken authored
-
Steve Holme authored
-
Marc Hoersken authored
-
David Ryskalczyk authored
Original commit message was: Don't omit CN verification in SChannel when an IP address is used. Side-effect of this change: SChannel and CryptoAPI do not support the iPAddress subjectAltName according to RFC 2818. If present, SChannel will first compare the IP address to the dNSName subjectAltNames and then fallback to the most specific Common Name in the Subject field of the certificate. This means that after this change curl will not connect to SSL/TLS hosts as long as the IP address is not specified in the SAN or CN of the server certificate or the verifyhost option is disabled.
-
Steve Holme authored
-
Marc Hoersken authored
Compilation was not possible if manuel is disabled due this error: error: macro "hugehelp" passed 1 arguments, but takes just 0 void hugehelp(void) {}
-
Steve Holme authored
-
- Feb 23, 2014
-
-
David Ryskalczyk authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
To allow for the addition of a global config structure and prevent confusion between the two.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
- Feb 22, 2014
-
-
Steve Holme authored
In preparation for separating the global config options from the per operation config options, reworked the list engines code to not use a member variable in the Configurable structure.
-
Steve Holme authored
To help assist with the detection of incorrect return codes, as per commits ee23d13a, 33b8960d and aba98991, updated the operate based functions to return CURLcode error codes.
-