WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.

Commit f6614759 authored Jan 28, 2005 by Daniel Stenberg

Connect failures with the multi interface was often returned as "connect()

timed out" even though the reason was different. Fixed this problem by not
setting this timeout to zero when using multi.

parent 54b02ecf

CHANGES

+4 −0

Original line number	Original line	Diff line number	Diff line
	@@ -6,6 +6,10 @@

	Changelog		Changelog

			Daniel (29 January 2005)
			- Connect failures with the multi interface was often returned as "connect()
			timed out" even though the reason was different.

	Daniel (28 January 2005)		Daniel (28 January 2005)
	- KNOWN_BUGS #17 fixed. A DNS cache entry may not remain locked between two		- KNOWN_BUGS #17 fixed. A DNS cache entry may not remain locked between two
	curl_easy_perform() invokes. It was previously unlocked at disconnect, which		curl_easy_perform() invokes. It was previously unlocked at disconnect, which

lib/connect.c

+1 −1

Original line number	Original line	Diff line number	Diff line
	@@ -754,7 +754,7 @@ CURLcode Curl_connecthost(struct connectdata conn, / context */

	if(data->state.used_interface == Curl_if_multi)		if(data->state.used_interface == Curl_if_multi)
	/* don't hang when doing multi */		/* don't hang when doing multi */
	timeout_per_addr = timeout_ms = 0;		timeout_per_addr = 0;

	/*		/*
	* Connecting with a Curl_addrinfo chain		* Connecting with a Curl_addrinfo chain