- Dec 06, 2014
-
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
Aligned continuation character and used space as the separator character as per other makefile files.
-
Steve Holme authored
...and minor layout adjustment.
-
- Dec 05, 2014
-
-
Patrick Monnerat authored
-
Patrick Monnerat authored
-
Steve Holme authored
multi.c:2695: warning: declaration of `exp' shadows a global declaration
-
Guenter Knauf authored
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
As it is often difficult to choose the best description for a single feature when it spans many commits, updated the descriptions for the recent SMB/CIFS protocol and GSS-API additions.
-
Steve Holme authored
-
Steve Holme authored
Don't use a hard coded size of 4 for the security layer and buffer size in Curl_sasl_create_gssapi_security_message(), instead, use sizeof() as we have done in the sasl_gssapi module.
-
Steve Holme authored
Reduced the amount of free's required for the decoded challenge message in Curl_sasl_create_gssapi_security_message() as a result of coding it differently in the sasl_gssapi module.
-
Steve Holme authored
-
Steve Holme authored
-
- Dec 04, 2014
-
-
Stefan Bühler authored
...they never have a body
-
Stefan Bühler authored
Sending NTLM/Negotiate header again after successful authentication breaks the connection with certain Proxies and request types (POST to MS Forefront).
-
Stefan Bühler authored
... similarly to how NTLM works as Negotiate is in fact often NTLM with another name.
-
Stefan Bühler authored
-
Steve Holme authored
-
Jay Satiro authored
Prior to this change the 10-at-a-time example showed CURLE_RECV_ERROR for the sony website because it ends the connection when the request is missing a user agent.
-
Steve Holme authored
-
Steve Holme authored
-
Steve Holme authored
-
Anthon Pang authored
It returns error for >= 400 HTTP responses. Bug: https://github.com/bagder/curl/pull/129
-
Peter Wu authored
Mark CURLOPT_UNIX_SOCKET_PATH as string to ensure that it ends up as option in the file generated by --libcurl. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Peter Wu authored
Add .nf and .fi such that the code gets wrapped in a pre on the web. Fixed grammar, fixed formatting of the "See also" items. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Patrick Monnerat authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
-
Daniel Stenberg authored
Otherwise we may read uninitialized bytes later in the unix-domain sockets case.
-
Daniel Stenberg authored
-
Peter Wu authored
Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Peter Wu authored
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. T...
-
Peter Wu authored
test1435: a simple test that checks whether a HTTP request can be performed over the UNIX socket. The hostname/port are interpreted by sws and should be ignored by cURL. test1436: test for the ability to do two requests to the same host, interleaved with one to a different hostname. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Peter Wu authored
The variable `$ipvnum` can now contain "unix" besides the integers 4 and 6 since the variable. Functions which receive this parameter have their `$port` parameter renamed to `$port_or_path` to support a path to the UNIX domain socket (as a "port" is only meaningful for TCP). Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Peter Wu authored
If sws is killed it might leave a stale socket file on the filesystem which would cause an EADDRINUSE error. After this patch, it is checked whether the socket is really stale and if so, the socket file gets removed and another bind is executed. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Peter Wu authored
This extends sws with a --unix-socket option which causes the port to be ignored (as the server now listens on the path specified by --unix-socket). This feature will be available in the following patch that enables checking for UNIX domain socket support. Proxy support (CONNECT) is not considered nor tested. It does not make sense anyway, first connecting through a TCP proxy, then let that TCP proxy connect to a UNIX socket. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-
Peter Wu authored
TCP_NODELAY does not make sense for Unix sockets, so enable it only if the socket is using IP. Signed-off-by: Peter Wu <peter@lekensteyn.nl>
-