cURL / Mailing Lists / curl-library / Single Mail


Re: cant resolve host on visual studio 2013

From: Azat Manukyan <>
Date: Wed, 4 Mar 2015 23:25:51 +0400

Hi Ray,

Thank you very much for your support, I made it to work on my pc. So here
is some information, it my be useful for future.
information about my environment

   1. I'm using the Windows 10 technical preview
   2. the curl version is the last one (actual I checked out from git)
   3. I use the OpenSSL of version 1.0.1i( at last, this version is
   mentioned in changes.txt file)
   4. and the development environment is visual studio 2013

Turns out that the problem was in curl_global_init(CURL_GLOBAL_SSL). I
don't no why but when i canged the CURL_GLOBAL_SSL parameter to CURL_GLOBAL_ALL
the lib starts work on windows.

if you need some additional information about my case i'll gladly will
share it with you. (except the host adders, sorry but at this moment i
can't provide it)

one more time thank you.

On 3 March 2015 at 22:29, Ray Satiro via curl-library <> wrote:

> On 3/3/2015 11:06 AM, Azat Manukyan wrote:
>> in both cases I haven't configured libcurl to any resolver.I supposed
>> that didn't need to configure any resolver.firewall is turned of on windows.
>> DNS resolver is working on windows environment because i can ping to
>> given host, and system log viewer does not give any issues.
>> So that is all that i can tall at this moment, if you need some other
>> information I will provide to You. I really need to work with this lib in
>> windows environment.
> When you use libcurl to access other hosts do you have the same problem?
> Is it possible you have an anti-virus or anti-malware client that may be
> blocking your program? What about when you try through your browser, can
> you access that host or other hosts? How about using the curl tool? Your
> test example looks straightforward, try the curl tool:
> curl -v -k -H "Content-Type: application/json" -d
> "{\"username\":\"name\",\"password\":\"test\"}"
> Note that the -k option allows insecure HTTPS connections and although
> keeping in line with your example you really should verify the server's
> certificate.
> If the curl tool doesn't work try using a curl tool that is known to work
> [1] rather than one you built yourself. Doing these things should help you
> narrow down a cause. If you need more assistance reply to the list with the
> details outlined in section 1.3 at [2].
> [1]:
> [2]:
> -------------------------------------------------------------------
> List admin:
> Etiquette:

List admin:
Received on 2015-03-04