On Tue, 14 Aug 2018, Daniel Stenberg via curl-library wrote:
I would like us to...
To make sure we keep track of this, I filed a bug:
https://github.com/curl/curl/issues/2888
--
/ daniel.haxx.se
---
Unsubscribe:
On Thu, 16 Aug 2018, Lessandro Mariano via curl-library wrote:
Also are any risks associated with using CURLOPT_RESOLVE to set Server
Name?
There are unintended consequences, for instance if you configure a proxy
curl will attempt to create a tunnel connection to the server name instead
of
On 30 July 2018 at 07:01, Alisha Joshi wrote:
> Also are any risks associated with using CURLOPT_RESOLVE to set Server
> Name?
There are unintended consequences, for instance if you configure a
proxy curl will attempt to create a tunnel connection to the server
name instead of the resolved ip
On Thu, 16 Aug 2018, Alisha Joshi via curl-library wrote:
If I use CURLOPT_RESOLVE, it is expected that I also have to do DNS
resolution in my application and get the IP before calling CURLOPT_RESOLVE,
right?
It is expected that you pass on the IP address to use. How you find that
address
