Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: CURLOPT_RESOLVE problem
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Thu, 19 Nov 2020 16:02:51 +0100 (CET)
On Thu, 19 Nov 2020, James Read via curl-library wrote:
> == Info: Couldn't parse CURLOPT_RESOLVE entry '
> http://kitcheneroktoberfest.com/:443:69.172.201.153'!
Quote from the docs:
Each single name resolve string should be written using the format
HOST:PORT:ADDRESS[,ADDRESS]... where HOST is the name libcurl will try
to resolve
You didn't pass on a host name there, it looks like an entire URL.
Date: Thu, 19 Nov 2020 16:02:51 +0100 (CET)
On Thu, 19 Nov 2020, James Read via curl-library wrote:
> == Info: Couldn't parse CURLOPT_RESOLVE entry '
> http://kitcheneroktoberfest.com/:443:69.172.201.153'!
Quote from the docs:
Each single name resolve string should be written using the format
HOST:PORT:ADDRESS[,ADDRESS]... where HOST is the name libcurl will try
to resolve
You didn't pass on a host name there, it looks like an entire URL.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/ ------------------------------------------------------------------- Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2020-11-19