KNOWN_BUGS: CURLOPT_CONNECT_TO does not work for HTTPS proxy #3185 Sign in to view logs Summary Jobs setup build-cache quictls gnutls wolfssl openssl-quic quiche Run details Usage Workflow file Triggered via push September 3, 2024 13:15 bagder pushed 933e202 master Status Success ...
connect_to = curl_slist_append(NULL, "mra-host.example.com::vcse.example.com:8443"); curl_easy_setopt(easyHandle, CURLOPT_CONNECT_TO, connect_to); curl_easy_setopt(easyHandle, CURLOPT_URL, "https://mra-host.example.com:8443/[...]); curl_easy_getinfo(easyHandle, CURLINFO_COOKIELI...
non-blocking curl_easy_send() and curl_easy_recv() ? To give some background, I am able to authenticate and able to work with the box with the blocked call ( without CURLOPT_CONNECT_ONLY option) with no control over the curl connection. The problem is, since the response from the bo...
Subject: RE: How to authenticate when using “CURLOPT_CONNECT_ONLY” so I can use non-blocking curl_easy_send() and curl_easy_recv() On Mon, 19 Jul 2021, Venkat Maddisetti via curl-library wrote: > Before coming here I realized curl_easy_setopt has no effect setting > username and ...
0 which makes it not used. This also makes port number zero impossible to set with this API. PROTOCOLS This functionality affects all supported protocols EXAMPLE int main(void) { CURL *curl = curl_easy_init(); if(curl) { CURLcode res; curl_easy_setopt(curl, CURLOPT_URL, "https://exa...
I did this I upgraded from libcurl 8.1.2 to 8.10.1 I use c-ares backend. I use multi interface and create a transfer with just 2 seconds of connect timeout: curl_easy_setopt(curl, CURLOPT_CONNECTTIMEOUT_MS, 2000L); I expected the followi...
Changes in curl 7.64.1 close cause curl to close the socket in the connection cache upon reuse if CURLOPT_CONNECT_ONLY and CURLOPT_MAXCONNECTS are both set to 1 - this makes using curl_send and curl_recv impossible because curl reports "Failed to get recent socket" I did this create an...
option) with no control over the curl connection. The problem is, since the response from the box is a stream of data there is no way for me to stop the stream and send an another request. So from the documentation I figured out “CURLOPT_CONNECT_ONLY” is the way to ...
> manage the communication to the box but after adding “CURLOPT_CONNECT_ONLY” > option, I am not receiving the data stream as expected, I guess my request > went through as there are no errors thrown, but looking closely I did not see ...
CURLOPT_USERPWD, CURLOPT_USERNAME and CURLOPT_PASSWORD included ? "POST /emp/ HTTP/1.1 If you want HTTP, then using CONNECT_ONLY + send/recv is *extremely* rarelythe right answer. You seem to want a plain POST with Basic auth and libcurl does that prettywell and simply with the regula...