From bd5d21aaf23cd20b74ad13e9d8ca16e81a4aea48 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 20 Oct 2006 12:25:39 +0000 Subject: When a resolve is made on a pipelined connection we need to detect it properly (when the resoling isn't completede yet) and not confuse it with a simple connection re-use (non-pipelined). --- lib/url.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/url.c') diff --git a/lib/url.c b/lib/url.c index 4bb4234f7..65453155c 100644 --- a/lib/url.c +++ b/lib/url.c @@ -3623,7 +3623,7 @@ static CURLcode CreateConnection(struct SessionHandle *data, conn->connectindex, conn->bits.httpproxy?conn->proxy.dispname:conn->host.dispname); #ifdef CURLRES_ASYNCH - if(!conn->dns_entry) { + if(!conn->ip_addr_str) { infof(data, "... but it is not resolved yet!\n"); *async = TRUE; } -- cgit v1.2.3