On Mon, 9 Jul 2012, Gisle Vanem wrote:
* Couldn't find host www.skandiabanken.se in the _netrc file; using defaults
* Re-using existing connection! (#0) with host (nil)
* Connected to (nil) (194.114.243.37) port 443 (#0)
Thanks for the excellent report. I've now pushed a fix that makes this
Daniel Stenberg dan...@haxx.se wrote:
Okay, but can you give me an exact command line you use to get it? I've not
yet managed to repeat this problem and I would like to, so that I can perhaps
make a test case for it.
Sorry for the delay. I forgot about this. But this example shows the
(nil)
On Thu, 7 Jun 2012, Gisle Vanem wrote:
Back to this topic after a month of nothing on it!
I don't get to see this. How do you get it like this? What name resolver is
this libcurl built to use?
The standard AFAICS. I used '-DENABLE_IPV6' and no C-ares; so CURLRES_IPV6
and CURLRES_SYNCH
When running curl --trace-ascii -, I see lots of such lines:
== Info: Re-using existing connection! (#0) with host (nil)
== Info: Connected to (nil) (194.103.154.240) port 443 (#0)
I mean, the (nil) looks ugly. So to give a nicer trace, when 'host.name' is
known, why not use that instead when
On Wed, 6 Jun 2012, Gisle Vanem wrote:
When running curl --trace-ascii -, I see lots of such lines:
== Info: Re-using existing connection! (#0) with host (nil)
== Info: Connected to (nil) (194.103.154.240) port 443 (#0)
I mean, the (nil) looks ugly. So to give a nicer trace, when 'host.name'
Daniel Stenberg dan...@haxx.se wrote.
I mean, the (nil) looks ugly. So to give a nicer trace, when 'host.name'
is known, why not use that instead when 'host.dispname' is NULL?
I don't get to see this. How do you get it like this? What name resolver is
this libcurl built to use?
The
