Andy Green eeea000ced dns: handle EAI_NONAME as fatal ... This causes the blocking dns lookup to treat EAI_NONAME as immediately fatal, this is usually caused by an assertive NXDOMAIN from the DNS server or similar. Not being able to reach the server should continue to retry. In order to make the problem visible, it reports the situation using CLIENT_CONNECTION_ERROR, even though it is still inside the outer client creation call.		2021-07-07 08:43:56 +01:00
..
client.c	type comparisons: fixes	2021-01-05 10:56:38 +00:00
conmon.c	cygwin: include in unix type socket init	2021-06-17 14:19:40 +01:00
connect.c	smp: fix client tsi detection	2021-05-20 14:07:25 +01:00
connect2.c	dns: handle EAI_NONAME as fatal	2021-07-07 08:43:56 +01:00
connect3.c	win32: client: just do WIN32 check	2021-06-20 07:21:31 +01:00
connect4.c	lws_metrics	2021-03-08 21:47:28 +00:00
sort-dns.c	cygwin: include in unix type socket init	2021-06-17 14:19:40 +01:00