Hello!
Please note that we would *love* your assistance here if you're a
Windows user and can offer a few moments of your time to run a few
tests on a few Windows versions and tell us the outcome! Here's a
simple way to help us make curl better without doing any coding at
all! =)
We want
Daniel Stenberg wrote:
On Wed, 6 Sep 2017, Ben Greear wrote:
Is there a good fix for this warning, or do I just need to turn off
strict warnings?
...
vtls/openssl.c: In function ‘ossl_connect_step1’:
vtls/openssl.c:2091:5: warning: ‘SSLv3_client_method’ is deprecated
Since commit bcca842e from last week "polarssl: fix hangs" my PolarSSL
autobuilds have been failing test 301 with "curl returned 56, when expecting
0". Error 56 is CURLE_RECV_ERROR. Has anyone else seen this?
I have fixed this with commit a7e4348. Thank you for reporting this!
Regards,
Michael
If no objections show up, I'll merge tomorrow.
Please replace "TLS_NODELAY" with "TCP_NODELAY" in the commit message
Regards,
Michael
---
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:
Do you want to authenticate against the reverse proxy or some server beyond
that? The latter case will never work with NTLM afaik unless the
reverse proxy
is transparent.
I am building the reverse proxy :-) It's like this:
Client <--> Reverse Proxy (uses libcurl) <--> Server
The client
Hi,
in my company, we use libcurl to forward requests in a reverse proxy
setup. We want to forward requests that use NTLM authentication. These
requests already have "Authentication: NTLM ..." headers, so libcurl's
CURLAUTH_NTLM feature is not suitable for such requests.
The problem is
> looking at the SessionHandle struct, and wondering: how do people
retrieve current values from the structure?
There is no official API to retrieve the current settings.
curl_easy_getinfo() is not the counterpart of curl_easy_setopt(), and
there is no curl_easy_getopt().
For options like
Hi,
the admin tool for the mailing lists at
http://cool.haxx.se/mailman/listinfo/curl-library stopped working: "Bug
in Mailman... we're sorry, we hit a bug"
Regards,
Michael
---
List admin:
Should we consider providing another pointer for the OpenSSL backend?
Sure, I'm open for discussions and solutions!
Yes, please consider this. I propose to add a new CURLINFO constant,
because the existing API must not be changed (backwards compatibility).
We could call it
Hi,
Currently, libcurl rejects responses with Content-Encoding: compress
when CURLOPT_ACCEPT_ENCODING is set to . I think that libcurl should
treat the Content-Encoding compress the same as other
Content-Encodings that it does not support, e.g. bzip2. I have
attached a patch for this.
Hi,
From the documentation of curl_share_setopt:
Cached DNS hosts will be shared across the easy handles using this
shared object. Note that when you use the multi interface, all easy
handles added to the same multi handle will share DNS cache by
default without this having to be used!
What about adding the connection cache to the share object? The SSL
session IDs are already part of it, so adding the connection cache
seems reasonable.
I always intended to have the connection cache to also be shareable
with the share interface and I think it would fit the existing
As suggested in many mails on this mailing list, I have tried to
solve this using CURLOPT_RESOLVE. I have found two problems:
Let me suggeset yet another way with existing functionality:
Use the share interface, and tell each easy handle that uses those
host names to use its own share
Hi,
I have a challenging scenario for libcurl. I want to connect with
https to a cluster of ADFS hosts (Active Directory Federation
Services). These hosts have the same hostname, but different IP
addresses. For example:
- host.example.org, IP: 10.0.0.1
- host.example.org, IP: 10.0.0.2
, 2015 at 1:10 PM, Michael Kaufmann m...@michael-kaufmann.ch
wrote:
Hi,
I have a challenging scenario for libcurl. I want to connect with https to
a cluster of ADFS hosts (Active Directory Federation Services). These hosts
have the same hostname, but different IP addresses. For example
Hi,
the documentation for CURLOPT_SEEKFUNCTION should mention that the
seek function is also needed if an HTTP server closes an existing
connection while curl is trying to reuse it.
I have attached a patch. Feel free to improve it :-)
Regards,
Michael
diff --git
16 matches
Mail list logo