1 _ _ ____ _ 2 ___| | | | _ \| | 3 / __| | | | |_) | | 4 | (__| |_| | _ <| |___ 5 \___|\___/|_| \_\_____| 6 7 Known Bugs 8 9These are problems and bugs known to exist at the time of this release. Feel 10free to join in and help us correct one or more of these. Also be sure to 11check the changelog of the current development status, as one or more of these 12problems may have been fixed or changed somewhat since this was written. 13 14 1. HTTP 15 1.2 hyper is slow 16 1.5 Expect-100 meets 417 17 18 2. TLS 19 2.1 IMAPS connection fails with rustls error 20 2.3 Unable to use PKCS12 certificate with Secure Transport 21 2.4 Secure Transport will not import PKCS#12 client certificates without a password 22 2.5 Client cert handling with Issuer DN differs between backends 23 2.7 Client cert (MTLS) issues with Schannel 24 2.11 Schannel TLS 1.2 handshake bug in old Windows versions 25 2.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel 26 27 3. Email protocols 28 3.1 IMAP SEARCH ALL truncated response 29 3.2 No disconnect command 30 3.3 POP3 expects "CRLF.CRLF" eob for some single-line responses 31 3.4 AUTH PLAIN for SMTP is not working on all servers 32 3.5 APOP authentication fails on POP3 33 3.6 POP3 issue when reading small chunks 34 35 4. Command line 36 37 5. Build and portability issues 38 5.1 OS400 port requires deprecated IBM library 39 5.2 curl-config --libs contains private details 40 5.3 building for old macOS fails with gcc 41 5.5 cannot handle Unicode arguments in non-Unicode builds on Windows 42 5.6 cygwin: make install installs curl-config.1 twice 43 5.9 Utilize Requires.private directives in libcurl.pc 44 5.11 configure --with-gssapi with Heimdal is ignored on macOS 45 5.12 flaky CI builds 46 5.13 long paths are not fully supported on Windows 47 5.14 Windows Unicode builds use homedir in current locale 48 5.15 Unicode on Windows 49 50 6. Authentication 51 6.1 NTLM authentication and unicode 52 6.2 MIT Kerberos for Windows build 53 6.3 NTLM in system context uses wrong name 54 6.5 NTLM does not support password with § character 55 6.6 libcurl can fail to try alternatives with --proxy-any 56 6.7 Do not clear digest for single realm 57 6.9 SHA-256 digest not supported in Windows SSPI builds 58 6.10 curl never completes Negotiate over HTTP 59 6.11 Negotiate on Windows fails 60 6.12 cannot use Secure Transport with Crypto Token Kit 61 6.13 Negotiate against Hadoop HDFS 62 63 7. FTP 64 7.1 FTP upload fails if remembered dir is deleted 65 7.2 Implicit FTPS upload timeout 66 7.3 FTP with NOBODY and FAILONERROR 67 7.4 FTP with ACCT 68 7.5 FTPS upload, FileZilla, GnuTLS and close_notify 69 7.11 FTPS upload data loss with TLS 1.3 70 7.12 FTPS directory listing hangs on Windows with Schannel 71 72 9. SFTP and SCP 73 9.1 SFTP does not do CURLOPT_POSTQUOTE correct 74 9.2 wolfssh: publickey auth does not work 75 9.3 Remote recursive folder creation with SFTP 76 9.4 libssh blocking and infinite loop problem 77 9.5 cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!" 78 79 10. SOCKS 80 10.3 FTPS over SOCKS 81 82 11. Internals 83 11.1 gssapi library name + version is missing in curl_version_info() 84 11.2 error buffer not set if connection to multiple addresses fails 85 11.4 HTTP test server 'connection-monitor' problems 86 11.5 Connection information when using TCP Fast Open 87 88 12. LDAP 89 12.1 OpenLDAP hangs after returning results 90 12.2 LDAP on Windows does authentication wrong? 91 12.3 LDAP on Windows does not work 92 12.4 LDAPS requests to ActiveDirectory server hang 93 94 13. TCP/IP 95 13.2 Trying local ports fails on Windows 96 97 15. CMake 98 15.1 cmake outputs: no version information available 99 15.2 support build with GnuTLS 100 15.3 unusable tool_hugehelp.c with MinGW 101 15.6 uses -lpthread instead of Threads::Threads 102 15.7 generated .pc file contains strange entries 103 15.11 ExternalProject_Add does not set CURL_CA_PATH 104 15.13 CMake build with MIT Kerberos does not work 105 106 16. aws-sigv4 107 16.1 aws-sigv4 does not sign requests with * correctly 108 16.2 aws-sigv4 does not handle multipart/form-data correctly 109 16.3 aws-sigv4 has problems with particular URLs 110 16.6 aws-sigv4 does not behave well with AWS VPC Lattice 111 112 17. HTTP/2 113 17.1 HTTP/2 prior knowledge over proxy 114 17.2 HTTP/2 frames while in the connection pool kill reuse 115 17.3 ENHANCE_YOUR_CALM causes infinite retries 116 117 18. HTTP/3 118 18.1 connection migration does not work 119 18.2 quiche: QUIC connection is draining 120 121 19. RTSP 122 19.1 Some methods do not support response bodies 123 124============================================================================== 125 1261. HTTP 127 1281.2 hyper is slow 129 130 When curl is built to use hyper for HTTP, it is unnecessary slow. 131 132 https://github.com/curl/curl/issues/11203 133 1341.5 Expect-100 meets 417 135 136 If an upload using Expect: 100-continue receives an HTTP 417 response, it 137 ought to be automatically resent without the Expect:. A workaround is for 138 the client application to redo the transfer after disabling Expect:. 139 https://curl.se/mail/archive-2008-02/0043.html 140 1412. TLS 142 1432.1 IMAPS connection fails with rustls error 144 145 https://github.com/curl/curl/issues/10457 146 1472.3 Unable to use PKCS12 certificate with Secure Transport 148 149 See https://github.com/curl/curl/issues/5403 150 1512.4 Secure Transport will not import PKCS#12 client certificates without a password 152 153 libcurl calls SecPKCS12Import with the PKCS#12 client certificate, but that 154 function rejects certificates that do not have a password. 155 https://github.com/curl/curl/issues/1308 156 1572.5 Client cert handling with Issuer DN differs between backends 158 159 When the specified client certificate does not match any of the 160 server-specified DNs, the OpenSSL and GnuTLS backends behave differently. 161 The github discussion may contain a solution. 162 163 See https://github.com/curl/curl/issues/1411 164 1652.7 Client cert (MTLS) issues with Schannel 166 167 See https://github.com/curl/curl/issues/3145 168 1692.11 Schannel TLS 1.2 handshake bug in old Windows versions 170 171 In old versions of Windows such as 7 and 8.1 the Schannel TLS 1.2 handshake 172 implementation likely has a bug that can rarely cause the key exchange to 173 fail, resulting in error SEC_E_BUFFER_TOO_SMALL or SEC_E_MESSAGE_ALTERED. 174 175 https://github.com/curl/curl/issues/5488 176 1772.13 CURLOPT_CERTINFO results in CURLE_OUT_OF_MEMORY with Schannel 178 179 https://github.com/curl/curl/issues/8741 180 1813. Email protocols 182 1833.1 IMAP SEARCH ALL truncated response 184 185 IMAP "SEARCH ALL" truncates output on large boxes. "A quick search of the 186 code reveals that pingpong.c contains some truncation code, at line 408, when 187 it deems the server response to be too large truncating it to 40 characters" 188 https://curl.se/bug/view.cgi?id=1366 189 1903.2 No disconnect command 191 192 The disconnect commands (LOGOUT and QUIT) may not be sent by IMAP, POP3 and 193 SMTP if a failure occurs during the authentication phase of a connection. 194 1953.3 POP3 expects "CRLF.CRLF" eob for some single-line responses 196 197 You have to tell libcurl not to expect a body, when dealing with one line 198 response commands. Please see the POP3 examples and test cases which show 199 this for the NOOP and DELE commands. https://curl.se/bug/?i=740 200 2013.4 AUTH PLAIN for SMTP is not working on all servers 202 203 Specifying "--login-options AUTH=PLAIN" on the command line does not seem to 204 work correctly. 205 206 See https://github.com/curl/curl/issues/4080 207 2083.5 APOP authentication fails on POP3 209 210 See https://github.com/curl/curl/issues/10073 211 2123.6 POP3 issue when reading small chunks 213 214 CURL_DBG_SOCK_RMAX=4 ./runtests.pl -v 982 215 216 See https://github.com/curl/curl/issues/12063 217 2184. Command line 219 2205. Build and portability issues 221 2225.1 OS400 port requires deprecated IBM library 223 224 curl for OS400 requires QADRT to build, which provides ASCII wrappers for 225 libc/POSIX functions in the ILE, but IBM no longer supports or even offers 226 this library to download. 227 228 See https://github.com/curl/curl/issues/5176 229 2305.2 curl-config --libs contains private details 231 232 "curl-config --libs" will include details set in LDFLAGS when configure is 233 run that might be needed only for building libcurl. Further, curl-config 234 --cflags suffers from the same effects with CFLAGS/CPPFLAGS. 235 2365.3 building for old macOS fails with gcc 237 238 Building curl for certain old macOS versions fails when gcc is used. We 239 command using clang in those cases. 240 241 See https://github.com/curl/curl/issues/11441 242 2435.5 cannot handle Unicode arguments in non-Unicode builds on Windows 244 245 If a URL or filename cannot be encoded using the user's current codepage then 246 it can only be encoded properly in the Unicode character set. Windows uses 247 UTF-16 encoding for Unicode and stores it in wide characters, however curl 248 and libcurl are not equipped for that at the moment except when built with 249 _UNICODE and UNICODE defined. And, except for Cygwin, Windows cannot use UTF-8 250 as a locale. 251 252 https://curl.se/bug/?i=345 253 https://curl.se/bug/?i=731 254 https://curl.se/bug/?i=3747 255 2565.6 cygwin: make install installs curl-config.1 twice 257 258 https://github.com/curl/curl/issues/8839 259 2605.9 Utilize Requires.private directives in libcurl.pc 261 262 https://github.com/curl/curl/issues/864 263 2645.11 configure --with-gssapi with Heimdal is ignored on macOS 265 266 ... unless you also pass --with-gssapi-libs 267 268 https://github.com/curl/curl/issues/3841 269 2705.12 flaky CI builds 271 272 We run many CI builds for each commit and PR on github, and especially a 273 number of the Windows builds are flaky. This means that we rarely get all CI 274 builds go green and complete without errors. This is unfortunate as it makes 275 us sometimes miss actual build problems and it is surprising to newcomers to 276 the project who (rightfully) do not expect this. 277 278 See https://github.com/curl/curl/issues/6972 279 2805.13 long paths are not fully supported on Windows 281 282 curl on Windows cannot access long paths (paths longer than 260 characters). 283 However, as a workaround, the Windows path prefix \\?\ which disables all path 284 interpretation may work to allow curl to access the path. For example: 285 \\?\c:\longpath. 286 287 See https://github.com/curl/curl/issues/8361 288 2895.14 Windows Unicode builds use homedir in current locale 290 291 The Windows Unicode builds of curl use the current locale, but expect Unicode 292 UTF-8 encoded paths for internal use such as open, access and stat. The user's 293 home directory is retrieved via curl_getenv in the current locale and not as 294 UTF-8 encoded Unicode. 295 296 See https://github.com/curl/curl/pull/7252 and 297 https://github.com/curl/curl/pull/7281 298 2995.15 Unicode on Windows 300 301 Passing in a unicode filename with -o: 302 303 https://github.com/curl/curl/issues/11461 304 305 Passing in unicode character with -d: 306 307 https://github.com/curl/curl/issues/12231 308 3096. Authentication 310 3116.1 NTLM authentication and unicode 312 313 NTLM authentication involving unicode user name or password only works 314 properly if built with UNICODE defined together with the Schannel 315 backend. The original problem was mentioned in: 316 https://curl.se/mail/lib-2009-10/0024.html 317 https://curl.se/bug/view.cgi?id=896 318 319 The Schannel version verified to work as mentioned in 320 https://curl.se/mail/lib-2012-07/0073.html 321 3226.2 MIT Kerberos for Windows build 323 324 libcurl fails to build with MIT Kerberos for Windows (KfW) due to KfW's 325 library header files exporting symbols/macros that should be kept private to 326 the KfW library. See ticket #5601 at https://krbdev.mit.edu/rt/ 327 3286.3 NTLM in system context uses wrong name 329 330 NTLM authentication using SSPI (on Windows) when (lib)curl is running in 331 "system context" will make it use wrong(?) user name - at least when compared 332 to what winhttp does. See https://curl.se/bug/view.cgi?id=535 333 3346.5 NTLM does not support password with § character 335 336 https://github.com/curl/curl/issues/2120 337 3386.6 libcurl can fail to try alternatives with --proxy-any 339 340 When connecting via a proxy using --proxy-any, a failure to establish an 341 authentication will cause libcurl to abort trying other options if the 342 failed method has a higher preference than the alternatives. As an example, 343 --proxy-any against a proxy which advertise Negotiate and NTLM, but which 344 fails to set up Kerberos authentication will not proceed to try authentication 345 using NTLM. 346 347 https://github.com/curl/curl/issues/876 348 3496.7 Do not clear digest for single realm 350 351 https://github.com/curl/curl/issues/3267 352 3536.9 SHA-256 digest not supported in Windows SSPI builds 354 355 Windows builds of curl that have SSPI enabled use the native Windows API calls 356 to create authentication strings. The call to InitializeSecurityContext fails 357 with SEC_E_QOP_NOT_SUPPORTED which causes curl to fail with CURLE_AUTH_ERROR. 358 359 Microsoft does not document supported digest algorithms and that SEC_E error 360 code is not a documented error for InitializeSecurityContext (digest). 361 362 https://github.com/curl/curl/issues/6302 363 3646.10 curl never completes Negotiate over HTTP 365 366 Apparently it is not working correctly...? 367 368 See https://github.com/curl/curl/issues/5235 369 3706.11 Negotiate on Windows fails 371 372 When using --negotiate (or NTLM) with curl on Windows, SSL/TLS handshake 373 fails despite having a valid kerberos ticket cached. Works without any issue 374 in Unix/Linux. 375 376 https://github.com/curl/curl/issues/5881 377 3786.12 cannot use Secure Transport with Crypto Token Kit 379 380 https://github.com/curl/curl/issues/7048 381 3826.13 Negotiate authentication against Hadoop HDFS 383 384 https://github.com/curl/curl/issues/8264 385 3867. FTP 387 3887.1 FTP upload fails if remembered dir is deleted 389 390 curl's FTP code assumes that the directory it entered in a previous transfer 391 still exists when it comes back to do a second transfer, and does not respond 392 well if it was indeed deleted in the mean time. 393 394 https://github.com/curl/curl/issues/12181 395 3967.2 Implicit FTPS upload timeout 397 398 https://github.com/curl/curl/issues/11720 399 4007.3 FTP with NOBODY and FAILONERROR 401 402 It seems sensible to be able to use CURLOPT_NOBODY and CURLOPT_FAILONERROR 403 with FTP to detect if a file exists or not, but it is not working: 404 https://curl.se/mail/lib-2008-07/0295.html 405 4067.4 FTP with ACCT 407 408 When doing an operation over FTP that requires the ACCT command (but not when 409 logging in), the operation will fail since libcurl does not detect this and 410 thus fails to issue the correct command: 411 https://curl.se/bug/view.cgi?id=635 412 4137.5 FTPS upload, FileZilla, GnuTLS and close_notify 414 415 An issue where curl does not send the TLS alert close_notify, which triggers 416 the wrath of GnuTLS in FileZilla server, and a FTP reply 426 ECONNABORTED. 417 418 https://github.com/curl/curl/issues/11383 419 4207.11 FTPS upload data loss with TLS 1.3 421 422 During FTPS upload curl does not attempt to read TLS handshake messages sent 423 after the initial handshake. OpenSSL servers running TLS 1.3 may send such a 424 message. When curl closes the upload connection if unread data has been 425 received (such as a TLS handshake message) then the TCP protocol sends an 426 RST to the server, which may cause the server to discard or truncate the 427 upload if it has not read all sent data yet, and then return an error to curl 428 on the control channel connection. 429 430 Since 7.78.0 this is mostly fixed. curl will do a single read before closing 431 TLS connections (which causes the TLS library to read handshake messages), 432 however there is still possibility of an RST if more messages need to be read 433 or a message arrives after the read but before close (network race condition). 434 435 https://github.com/curl/curl/issues/6149 436 4377.12 FTPS server compatibility on Windows with Schannel 438 439 FTPS is not widely used with the Schannel TLS backend and so there may be more 440 bugs compared to other TLS backends such as OpenSSL. In the past users have 441 reported hanging and failed connections. It's very likely some changes to curl 442 since then fixed the issues. None of the reported issues can be reproduced any 443 longer. 444 445 If you encounter an issue connecting to your server via FTPS with the latest 446 curl and Schannel then please search for open issues or file a new issue. 447 4489. SFTP and SCP 449 4509.1 SFTP does not do CURLOPT_POSTQUOTE correct 451 452 When libcurl sends CURLOPT_POSTQUOTE commands when connected to a SFTP server 453 using the multi interface, the commands are not being sent correctly and 454 instead the connection is "cancelled" (the operation is considered done) 455 prematurely. There is a half-baked (busy-looping) patch provided in the bug 456 report but it cannot be accepted as-is. See 457 https://curl.se/bug/view.cgi?id=748 458 4599.2 wolfssh: publickey auth does not work 460 461 When building curl to use the wolfSSH backend for SFTP, the publickey 462 authentication does not work. This is simply functionality not written for curl 463 yet, the necessary API for make this work is provided by wolfSSH. 464 465 See https://github.com/curl/curl/issues/4820 466 4679.3 Remote recursive folder creation with SFTP 468 469 On this servers, the curl fails to create directories on the remote server 470 even when the CURLOPT_FTP_CREATE_MISSING_DIRS option is set. 471 472 See https://github.com/curl/curl/issues/5204 473 4749.4 libssh blocking and infinite loop problem 475 476 In the SSH_SFTP_INIT state for libssh, the ssh session working mode is set to 477 blocking mode. If the network is suddenly disconnected during sftp 478 transmission, curl will be stuck, even if curl is configured with a timeout. 479 480 https://github.com/curl/curl/issues/8632 481 4829.5 cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!" 483 484 Running SCP and SFTP tests on cygwin makes this warning message appear. 485 486 https://github.com/curl/curl/issues/11244 487 48810. SOCKS 489 49010.3 FTPS over SOCKS 491 492 libcurl does not support FTPS over a SOCKS proxy. 493 494 49511. Internals 496 49711.1 gssapi library name + version is missing in curl_version_info() 498 499 The struct needs to be expanded and code added to store this info. 500 501 See https://github.com/curl/curl/issues/13492 502 50311.2 error buffer not set if connection to multiple addresses fails 504 505 If you ask libcurl to resolve a hostname like example.com to IPv6 addresses 506 only. But you only have IPv4 connectivity. libcurl will correctly fail with 507 CURLE_COULDNT_CONNECT. But the error buffer set by CURLOPT_ERRORBUFFER 508 remains empty. Issue: https://github.com/curl/curl/issues/544 509 51011.4 HTTP test server 'connection-monitor' problems 511 512 The 'connection-monitor' feature of the sws HTTP test server does not work 513 properly if some tests are run in unexpected order. Like 1509 and then 1525. 514 515 See https://github.com/curl/curl/issues/868 516 51711.5 Connection information when using TCP Fast Open 518 519 CURLINFO_LOCAL_PORT (and possibly a few other) fails when TCP Fast Open is 520 enabled. 521 522 See https://github.com/curl/curl/issues/1332 and 523 https://github.com/curl/curl/issues/4296 524 52512. LDAP 526 52712.1 OpenLDAP hangs after returning results 528 529 By configuration defaults, OpenLDAP automatically chase referrals on 530 secondary socket descriptors. The OpenLDAP backend is asynchronous and thus 531 should monitor all socket descriptors involved. Currently, these secondary 532 descriptors are not monitored, causing OpenLDAP library to never receive 533 data from them. 534 535 As a temporary workaround, disable referrals chasing by configuration. 536 537 The fix is not easy: proper automatic referrals chasing requires a 538 synchronous bind callback and monitoring an arbitrary number of socket 539 descriptors for a single easy handle (currently limited to 5). 540 541 Generic LDAP is synchronous: OK. 542 543 See https://github.com/curl/curl/issues/622 and 544 https://curl.se/mail/lib-2016-01/0101.html 545 54612.2 LDAP on Windows does authentication wrong? 547 548 https://github.com/curl/curl/issues/3116 549 55012.3 LDAP on Windows does not work 551 552 A simple curl command line getting "ldap://ldap.forumsys.com" returns an 553 error that says "no memory" ! 554 555 https://github.com/curl/curl/issues/4261 556 55712.4 LDAPS requests to ActiveDirectory server hang 558 559 https://github.com/curl/curl/issues/9580 560 56113. TCP/IP 562 56313.2 Trying local ports fails on Windows 564 565 This makes '--local-port [range]' to not work since curl cannot properly 566 detect if a port is already in use, so it will try the first port, use that and 567 then subsequently fail anyway if that was actually in use. 568 569 https://github.com/curl/curl/issues/8112 570 57115. CMake 572 57315.1 cmake outputs: no version information available 574 575 Something in the SONAME generation seems to be wrong in the cmake build. 576 577 https://github.com/curl/curl/issues/11158 578 57915.2 support build with GnuTLS 580 58115.3 unusable tool_hugehelp.c with MinGW 582 583 see https://github.com/curl/curl/issues/3125 584 58515.6 uses -lpthread instead of Threads::Threads 586 587 See https://github.com/curl/curl/issues/6166 588 58915.7 generated .pc file contains strange entries 590 591 The Libs.private field of the generated .pc file contains -lgcc -lgcc_s -lc 592 -lgcc -lgcc_s 593 594 See https://github.com/curl/curl/issues/6167 595 59615.11 ExternalProject_Add does not set CURL_CA_PATH 597 598 CURL_CA_BUNDLE and CURL_CA_PATH are not set properly when cmake's 599 ExternalProject_Add is used to build curl as a dependency. 600 601 See https://github.com/curl/curl/issues/6313 602 60315.13 CMake build with MIT Kerberos does not work 604 605 Minimum CMake version was bumped in curl 7.71.0 (#5358) Since CMake 3.2 606 try_compile started respecting the CMAKE_EXE_FLAGS. The code dealing with 607 MIT Kerberos detection sets few variables to potentially weird mix of space, 608 and ;-separated flags. It had to blow up at some point. All the CMake checks 609 that involve compilation are doomed from that point, the configured tree 610 cannot be built. 611 612 https://github.com/curl/curl/issues/6904 613 61416. aws-sigv4 615 61616.1 aws-sigv4 does not sign requests with * correctly 617 618 https://github.com/curl/curl/issues/7559 619 62016.2 aws-sigv4 does not handle multipart/form-data correctly 621 622 https://github.com/curl/curl/issues/13351 623 62416.3 aws-sigv4 has problems with particular URLs 625 626 https://github.com/curl/curl/issues/13058 627 62816.6 aws-sigv4 does not behave well with AWS VPC Lattice 629 630 https://github.com/curl/curl/issues/11007 631 63217. HTTP/2 633 63417.1 HTTP/2 prior knowledge over proxy 635 636 https://github.com/curl/curl/issues/12641 637 63817.2 HTTP/2 frames while in the connection pool kill reuse 639 640 If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to 641 curl while the connection is held in curl's connection pool, the socket will 642 be found readable when considered for reuse and that makes curl think it is 643 dead and then it will be closed and a new connection gets created instead. 644 645 This is *best* fixed by adding monitoring to connections while they are kept 646 in the pool so that pings can be responded to appropriately. 647 64817.3 ENHANCE_YOUR_CALM causes infinite retries 649 650 Infinite retries with 2 parallel requests on one connection receiving GOAWAY 651 with ENHANCE_YOUR_CALM error code. 652 653 See https://github.com/curl/curl/issues/5119 654 65518. HTTP/3 656 65718.1 connection migration does not work 658 659 https://github.com/curl/curl/issues/7695 660 66118.2 quiche: QUIC connection is draining 662 663 The transfer ends with error "QUIC connection is draining". 664 665 https://github.com/curl/curl/issues/12037 666 66719. RTSP 668 66919.1 Some methods do not support response bodies 670 671 The RTSP implementation is written to assume that a number of RTSP methods 672 will always get responses without bodies, even though there seems to be no 673 indication in the RFC that this is always the case. 674 675 https://github.com/curl/curl/issues/12414 676
