#
92c2a4c0 |
| 17-Feb-2016 |
Tatsuhiro Tsujikawa |
http2: Add handling stream level error Previously, when a stream was closed with other than NGHTTP2_NO_ERROR by RST_STREAM, underlying TCP connection was dropped. This is undesirabl
http2: Add handling stream level error Previously, when a stream was closed with other than NGHTTP2_NO_ERROR by RST_STREAM, underlying TCP connection was dropped. This is undesirable since there may be other streams multiplexed and they are very much fine. This change introduce new error code CURLE_HTTP2_STREAM, which indicates stream error that only affects the relevant stream, and connection should be kept open. The existing CURLE_HTTP2 means connection error in general. Ref: https://github.com/curl/curl/issues/659 Ref: https://github.com/curl/curl/pull/663
show more ...
|
#
ccf7a826 |
| 09-Apr-2016 |
Steve Holme |
CURLOPT_SOCKS5_GSSAPI_SERVICE: Merged with CURLOPT_PROXY_SERVICE_NAME As these two options provide identical functionality, the former for SOCK5 proxies and the latter for HTTP proxies,
CURLOPT_SOCKS5_GSSAPI_SERVICE: Merged with CURLOPT_PROXY_SERVICE_NAME As these two options provide identical functionality, the former for SOCK5 proxies and the latter for HTTP proxies, merged the two options together. As such CURLOPT_SOCKS5_GSSAPI_SERVICE is marked as deprecated as of 7.49.0.
show more ...
|
#
4edcfc6b |
| 01-Apr-2016 |
Steve Holme |
test1119: Fixed missing CURL_DID_MEMORY_FUNC_TYPEDEFS symbol
|
#
324a97ec |
| 18-Mar-2016 |
Diego Bes |
http2: support "prior knowledge", no upgrade from HTTP/1.1 Supports HTTP/2 over clear TCP - Optimize switching to HTTP/2 by removing calls to init and setup before switching. Sw
http2: support "prior knowledge", no upgrade from HTTP/1.1 Supports HTTP/2 over clear TCP - Optimize switching to HTTP/2 by removing calls to init and setup before switching. Switching will eventually call setup and setup calls init. - Supports new version to “force” the use of HTTP/2 over clean TCP - Add common line parameter “--http2-prior-knowledge” to the Curl command line tool.
show more ...
|
#
332414a3 |
| 24-Feb-2016 |
Jay Satiro |
getinfo: CURLINFO_TLS_SSL_PTR supersedes CURLINFO_TLS_SESSION The two options are almost the same, except in the case of OpenSSL: CURLINFO_TLS_SESSION OpenSSL session internals is S
getinfo: CURLINFO_TLS_SSL_PTR supersedes CURLINFO_TLS_SESSION The two options are almost the same, except in the case of OpenSSL: CURLINFO_TLS_SESSION OpenSSL session internals is SSL_CTX *. CURLINFO_TLS_SSL_PTR OpenSSL session internals is SSL *. For backwards compatibility we couldn't modify CURLINFO_TLS_SESSION to return an SSL pointer for OpenSSL. Also, add support for the 'internals' member to point to SSL object for the other backends axTLS, PolarSSL, Secure Channel, Secure Transport and wolfSSL. Bug: https://github.com/curl/curl/issues/234 Reported-by: dkjjr89@users.noreply.github.com Bug: https://curl.haxx.se/mail/lib-2015-09/0127.html Reported-by: Michael König
show more ...
|
Revision tags: curl-7_46_0, curl-7_45_0 |
|
#
9dc3eaee |
| 17-Aug-2015 |
Michael Koenig |
TFTP: add option to suppress TFTP option requests (Part 1) Some TFTP server implementations ignore the "TFTP Option extension" (RFC 1782-1784, 2347-2349), or implement it in a flawed way
TFTP: add option to suppress TFTP option requests (Part 1) Some TFTP server implementations ignore the "TFTP Option extension" (RFC 1782-1784, 2347-2349), or implement it in a flawed way, causing problems with libcurl. Another switch for curl_easy_setopt "CURLOPT_TFTP_NO_OPTIONS" is introduced which prevents libcurl from sending TFTP option requests to a server, avoiding many problems caused by faulty implementations. Bug: https://github.com/curl/curl/issues/481
show more ...
|
#
4bcc532d |
| 13-Dec-2015 |
Daniel Stenberg |
http: add libcurl option to allow HTTP/2 for HTTPS only ... and stick to 1.1 for HTTP. This is in line with what browsers do and should have very little risk.
|
#
b1f9424f |
| 03-Dec-2015 |
Gisle Vanem |
version: Add flag CURL_VERSION_PSL for libpsl
|
#
1ee0aded |
| 13-Nov-2015 |
Steve Holme |
symbols-in-versions: Added new CURLOPTTYPE_STRINGPOINT alias ...following commit aba281e762 to fix test 1119.
|
#
cba5bc58 |
| 02-Nov-2015 |
Daniel Stenberg |
symbols-in-version: add all CURL_HTTPPOST_* symbols
|
#
ca5f9341 |
| 23-Oct-2015 |
Daniel Stenberg |
formadd: support >2GB files on windows Closes #425
|
#
d31ed6ac |
| 21-Oct-2015 |
Daniel Stenberg |
http2: s/priority/weight
|
#
fe7590f7 |
| 19-Oct-2015 |
Jonas Minnberg |
vtls: added support for mbedTLS closes #496
|
#
62f306ff |
| 21-Aug-2015 |
Razvan Cojocaru |
getinfo: added CURLINFO_ACTIVESOCKET This patch addresses known bug #76, where on 64-bit Windows SOCKET is 64 bits wide, but long is only 32, making CURLINFO_LASTSOCKET unreliable.
getinfo: added CURLINFO_ACTIVESOCKET This patch addresses known bug #76, where on 64-bit Windows SOCKET is 64 bits wide, but long is only 32, making CURLINFO_LASTSOCKET unreliable. Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
show more ...
|
#
9756d1da |
| 23-Aug-2015 |
Nathaniel Waisbrot
|
CURLOPT_DEFAULT_PROTOCOL: added - Add new option CURLOPT_DEFAULT_PROTOCOL to allow specifying a default protocol for schemeless URLs. - Add new tool option --proto-default to ex
CURLOPT_DEFAULT_PROTOCOL: added - Add new option CURLOPT_DEFAULT_PROTOCOL to allow specifying a default protocol for schemeless URLs. - Add new tool option --proto-default to expose CURLOPT_DEFAULT_PROTOCOL. In the case of schemeless URLs libcurl will behave in this way: When the option is used libcurl will use the supplied default. When the option is not used, libcurl will follow its usual plan of guessing from the hostname and falling back to 'http'.
show more ...
|
Revision tags: curl-7_44_0 |
|
#
aab76af1 |
| 18-Jul-2015 |
Jay Satiro |
symbols-in-versions: Add new CURLSSLOPT_NO_REVOKE symbol
|
#
616cecfd |
| 30-Jun-2015 |
Jay Satiro |
symbols-in-versions: Add new http2 push symbols Prior to this change test 1119 failed due to the missing symbols.
|
Revision tags: curl-7_43_0 |
|
#
3587da9e |
| 05-Jun-2015 |
Daniel Stenberg |
curl.h: add CURL_HTTP_VERSION_2 The protocol is named "HTTP/2" after all. It is an alias for the existing CURL_HTTP_VERSION_2_0 enum.
|
#
7d0df07e |
| 12-May-2015 |
Daniel Stenberg |
symbols-in-versions: add CURLOPT_PIPEWAIT
|
#
783b3c7b |
| 08-May-2015 |
Daniel Stenberg |
http2: separate multiplex/pipelining + cleanup memory leaks
|
Revision tags: curl-7_42_1, curl-7_42_0 |
|
#
97c272e5 |
| 29-Mar-2015 |
Linus Nielsen |
Negotiate: custom service names for SPNEGO. * Add new options, CURLOPT_PROXY_SERVICE_NAME and CURLOPT_SERVICE_NAME. * Add new curl options, --proxy-service-name and --service-name.
|
#
aa5808b5 |
| 24-Mar-2015 |
Dan Fandrich |
symbols-in-versions: added CURLOPT_PATH_AS_IS
|
Revision tags: curl-7_41_0 |
|
#
4dcd25e1 |
| 14-Feb-2015 |
Alessandro Ghedini |
url: add CURLOPT_SSL_FALSESTART option This option can be used to enable/disable TLS False Start defined in the RFC draft-bmoeller-tls-falsestart.
|
Revision tags: curl-7_40_0, curl-7_39_0, curl-7_38_0, curl-7_37_1 |
|
#
3af90a6e |
| 16-Jun-2014 |
Alessandro Ghedini |
url: add CURLOPT_SSL_VERIFYSTATUS option This option can be used to enable/disable certificate status verification using the "Certificate Status Request" TLS extension defined in RFC6066
url: add CURLOPT_SSL_VERIFYSTATUS option This option can be used to enable/disable certificate status verification using the "Certificate Status Request" TLS extension defined in RFC6066 section 8. This also adds the CURLE_SSL_INVALIDCERTSTATUS error, to be used when the certificate status verification fails, and the Curl_ssl_cert_status_request() function, used to check whether the SSL backend supports the status_request extension.
show more ...
|
#
970c22f9 |
| 27-Nov-2014 |
Peter Wu |
libcurl: add UNIX domain sockets support The ability to do HTTP requests over a UNIX domain socket has been requested before, in Apr 2008 [0][1] and Sep 2010 [2]. While a discussion
libcurl: add UNIX domain sockets support The ability to do HTTP requests over a UNIX domain socket has been requested before, in Apr 2008 [0][1] and Sep 2010 [2]. While a discussion happened, no patch seems to get through. I decided to give it a go since I need to test a nginx HTTP server which listens on a UNIX domain socket. One patch [3] seems to make it possible to use the CURLOPT_OPENSOCKETFUNCTION function to gain a UNIX domain socket. Another person wrote a Go program which can do HTTP over a UNIX socket for Docker[4] which uses a special URL scheme (though the name contains cURL, it has no relation to the cURL library). This patch considers support for UNIX domain sockets at the same level as HTTP proxies / IPv6, it acts as an intermediate socket provider and not as a separate protocol. Since this feature affects network operations, a new feature flag was added ("unix-sockets") with a corresponding CURL_VERSION_UNIX_SOCKETS macro. A new CURLOPT_UNIX_SOCKET_PATH option is added and documented. This option enables UNIX domain sockets support for all requests on the handle (replacing IP sockets and skipping proxies). A new configure option (--enable-unix-sockets) and CMake option (ENABLE_UNIX_SOCKETS) can disable this optional feature. Note that I deliberately did not mark this feature as advanced, this is a feature/component that should easily be available. [0]: http://curl.haxx.se/mail/lib-2008-04/0279.html [1]: http://daniel.haxx.se/blog/2008/04/14/http-over-unix-domain-sockets/ [2]: http://sourceforge.net/p/curl/feature-requests/53/ [3]: http://curl.haxx.se/mail/lib-2008-04/0361.html [4]: https://github.com/Soulou/curl-unix-socket Signed-off-by: Peter Wu <peter@lekensteyn.nl>
show more ...
|