From 55ea2b424dc1d81f9488a5d6efac9dc980fe9e4a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Antoniak?= Date: Fri, 23 Jan 2026 16:51:44 +0100 Subject: [PATCH] setopt: fix checking range for CURLOPT_MAXCONNECTS - Use upper limit INT_MAX instead of UINT_MAX. UINT_MAX doesn't work as the max value for the variable since it is passed as a long and becomes -1 on platforms that have same sized int and long, like Windows. Closes https://github.com/curl/curl/pull/20414 --- lib/setopt.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lib/setopt.c b/lib/setopt.c index 2fc90c25ec..5034c4a5f0 100644 --- a/lib/setopt.c +++ b/lib/setopt.c @@ -851,9 +851,9 @@ static CURLcode setopt_long_net(struct Curl_easy *data, CURLoption option, s->dns_cache_timeout_ms = -1; break; case CURLOPT_MAXCONNECTS: - result = value_range(&arg, 1, 1, UINT_MAX); + result = value_range(&arg, 1, 1, INT_MAX); if(!result) - s->maxconnects = (unsigned int)arg; + s->maxconnects = (uint32_t)arg; break; case CURLOPT_SERVER_RESPONSE_TIMEOUT: return setopt_set_timeout_sec(&s->server_response_timeout, arg);