Artifactspublic-v0

curl

master
ply4 git calls31 ms294 KiB3 cachedprotocol v2
475 lines17 KiBRaw

Known bugs intro

These are problems and bugs known to exist at the time of this release. Feel free to join in and help us correct one or more of these. Also be sure to check the changelog of the current development status, as one or more of these problems may have been fixed or changed somewhat since this was written.

TLS

IMAPS connection fails with Rustls error

curl issue 10457

Access violation sending client cert with Schannel

When using Schannel to do client certs, curl sets PKCS12_NO_PERSIST_KEY to avoid leaking the private key into the filesystem. Unfortunately that flag instead seems to trigger a crash.

See curl issue 17626

Client cert (MTLS) issues with Schannel

See curl issue 3145

Schannel TLS 1.2 handshake bug in old Windows versions

In old versions of Windows such as 7 and 8.1 the Schannel TLS 1.2 handshake implementation likely has a bug that can rarely cause the key exchange to fail, resulting in error SEC_E_BUFFER_TOO_SMALL or SEC_E_MESSAGE_ALTERED.

curl issue 5488

mbedTLS and CURLE_AGAIN handling

curl issue 15801

Native CA roots incomplete on Windows with OpenSSL (or fork)

Certain Windows installations may be missing CA roots.

curl issue 20897 curl issue 12303

ECH not working through Proxy Tunnels

curl issue 22043

Email protocols

IMAP SEARCH ALL truncated response

IMAP SEARCH ALL truncates output on large boxes. "A quick search of the code reveals that pingpong.c contains some truncation code, at line 408, when it deems the server response to be too large truncating it to 40 characters"

https://curl.se/bug/view.cgi?id=1366

AUTH PLAIN for SMTP is not working on all servers

Specifying --login-options AUTH=PLAIN on the command line does not seem to work correctly.

See curl issue 4080

APOP authentication fails on POP3

See curl issue 10073

POP3 issue when reading small chunks

CURL_DBG_SOCK_RMAX=4 ./runtests.pl -v 982

See curl issue 12063

Command line

-T /dev/stdin may upload with an incorrect content length

-T stats the path to figure out its size in bytes to use it as Content-Length if it is a regular file.

The problem with that is that on BSD and some other UNIX systems (not Linux), open(path) may not give you a file descriptor with a 0 offset from the start of the file.

See curl issue 12177

-T - always uploads chunked

When the < shell operator is used. curl should realize that stdin is a regular file in this case, and that it can do a non-chunked upload, like it would do if you used -T file.

See curl issue 12171

Build and portability issues

OS400 port requires deprecated IBM library

curl for OS400 requires QADRT to build, which provides ASCII wrappers for libc/POSIX functions in the ILE, but IBM no longer supports or even offers this library to download.

See curl issue 5176

LDFLAGS passed too late making libs linked incorrectly

Compiling latest curl on HP-UX and linking against a custom OpenSSL (which is on the default loader/linker path), fails because the generated Makefile has LDFLAGS passed on after LIBS.

See curl issue 14893

Cygwin: make install installs curl-config.1 twice

curl issue 8839

flaky CI builds

We run many CI builds for each commit and PR on GitHub, and especially a number of the Windows builds are flaky. This means that we rarely get all CI builds go green and complete without errors. This is unfortunate as it makes us sometimes miss actual build problems and it is surprising to newcomers to the project who (rightfully) do not expect this.

See curl issue 6972

long paths are not fully supported on Windows

curl on Windows cannot access long paths (paths longer than 260 characters). As a workaround, the Windows path prefix \\?\ which disables all path interpretation may work to allow curl to access the path. For example: \\?\c:\longpath.

See curl issue 8361

Unicode on Windows

Passing in a Unicode filename with -o:

curl issue 11461

Passing in Unicode character with -d:

curl issue 12231

Windows Unicode builds use the home directory in current locale.

The Windows Unicode builds of curl use the current locale, but expect Unicode UTF-8 encoded paths for internal use such as open, access and stat. The user's home directory is retrieved via curl_getenv in the current locale and not as UTF-8 encoded Unicode.

See curl pull request 7252 and curl pull request 7281

Cannot handle Unicode arguments in non-Unicode builds on Windows

If a URL or filename cannot be encoded using the user's current code page then it can only be encoded properly in the Unicode character set. Windows uses UTF-16 encoding for Unicode and stores it in wide characters, however curl and libcurl are not equipped for that at the moment except when built with _UNICODE and UNICODE defined. Except for Cygwin, Windows cannot use UTF-8 as a locale.

https://curl.se/bug/?i=345 https://curl.se/bug/?i=731 https://curl.se/bug/?i=3747

The Schannel version verified to work as mentioned in https://curl.se/mail/lib-2012-07/0073.html

Authentication

--aws-sigv4 signs an empty payload hash for bodies not held in memory

--aws-sigv4 hashes only the in-memory POST fields when it computes the payload hash, so a request whose body comes from anywhere else is signed as if it had no body at all: the signature is computed over SHA256("") while a different body goes on the wire. This affects -F (multipart/form-data) and -T (PUT upload) alike.

aws:amz:<region>:s3 is not affected, because it sends and signs UNSIGNED-PAYLOAD instead. Every other service gets the empty hash, with no x-amz-content-sha256 header sent, and no warning.

curl issue 13351

Digest auth-int for PUT/POST

We do not support auth-int for Digest using PUT or POST

Digest does not care for domain

libcurl ignores the domain directive in Digest authentication challenges (WWW-Authenticate:). RFC 7616 defines it as a quoted, space-separated list of URIs that define the protection space.

MIT Kerberos for Windows build

libcurl fails to build with MIT Kerberos for Windows (KfW) due to its library header files exporting symbols/macros that should be kept private to the library.

libcurl can fail to try alternatives with --proxy-any

When connecting via a proxy using --proxy-any, a failure to establish an authentication causes libcurl to abort trying other options if the failed method has a higher preference than the alternatives. As an example, --proxy-any against a proxy which advertise Negotiate and something else, but which fails to set up Kerberos authentication does not proceed to try authentication using the other auth method.

curl issue 876

Do not clear digest for single realm

curl issue 3267

SHA-256 digest not supported in Windows SSPI builds

Windows builds of curl that have SSPI enabled use the native Windows API calls to create authentication strings. The call to InitializeSecurityContext fails with SEC_E_QOP_NOT_SUPPORTED which causes curl to fail with CURLE_AUTH_ERROR.

Microsoft does not document supported digest algorithms and that SEC_E error code is not a documented error for InitializeSecurityContext (digest).

curl issue 6302

FTP

FTP with ACCT

When doing an operation over FTP that requires the ACCT command (but not when logging in), the operation fails since libcurl does not detect this and thus fails to issue the correct command: https://curl.se/bug/view.cgi?id=635

FTPS server compatibility on Windows with Schannel

FTPS is not widely used with the Schannel TLS backend and so there may be more bugs compared to other TLS backends such as OpenSSL. In the past users have reported hanging and failed connections. It is likely some changes to curl since then fixed the issues. None of the reported issues can be reproduced any longer.

If you encounter an issue connecting to your server via FTPS with the latest curl and Schannel then please search for open issues or file a new issue.

SFTP and SCP

SFTP does not do CURLOPT_POSTQUOTE correct

When libcurl sends CURLOPT_POSTQUOTE commands when connected to an SFTP server using the multi interface, the commands are not being sent correctly and instead the connection is canceled (the operation is considered done) prematurely. There is a half-baked (busy-looping) patch provided in the bug report but it cannot be accepted as-is. See https://curl.se/bug/view.cgi?id=748

Remote recursive folder creation with SFTP

On this servers, the curl fails to create directories on the remote server even when the CURLOPT_FTP_CREATE_MISSING_DIRS option is set.

See curl issue 5204

libssh blocking and infinite loop problem

In the SSH_SFTP_INIT state for libssh, the ssh session working mode is set to blocking mode. If the network is suddenly disconnected during sftp transmission, curl is stuck, even if curl is configured with a timeout.

curl issue 8632

Cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!"

Running SCP and SFTP tests on Cygwin makes this warning message appear.

curl issue 11244

Connection

--interface with link-scoped IPv6 address

When you give the --interface option telling curl to use a specific interface for its outgoing traffic in combination with an IPv6 address in the URL that uses a link-local scope, curl might pick the wrong address from the named interface and the subsequent transfer fails.

Example command line:

curl --interface eth0 'http://[fe80:928d:xxff:fexx:xxxx]/'

The fact that the given IP address is link-scoped should probably be used as input to somehow make curl make a better choice for this.

curl issue 14782

Does not acknowledge getaddrinfo sorting policy

Even if a user edits /etc/gai.conf to prefer IPv4, curl still prefers and tries IPv6 addresses first.

curl issue 16718

SOCKS-SSPI discards the security context

After a successful SSPI/GSS-API exchange, the function queries and logs the authenticated username and reports the supported data-protection level, but then immediately deletes the negotiated SSPI security context and frees the credentials before returning. The negotiated context is not stored on the connection and is therefore never used to protect later SOCKS5 traffic.

cannot use absolute Unix domain filename for SOCKS on Windows

curl supports using a Unix domain socket path for speaking SOCKS to a proxy, by providing a filename in the URL used for -x (CURLOPT_PROXY), but that path cannot be a proper absolute Windows path with a drive letter etc.

A solution for this probably requires that we add and provide a --unix-socket (CURLOPT_UNIX_SOCKET_PATH) option alternative for proxy communication.

See curl issue 19825

Internals

GSSAPI library name + version is missing in curl_version_info()

The struct needs to be expanded and code added to store this info.

See curl issue 13492

HTTP test server 'connection-monitor' problems

The connection-monitor feature of the HTTP test server does not work properly if some tests are run in unexpected order. Like 1509 and then 1525.

See curl issue 868

Connection information when using TCP Fast Open

CURLINFO_LOCAL_PORT (and possibly a few other) fails when TCP Fast Open is enabled.

See curl issue 1332 and curl issue 4296

test cases sometimes timeout

Occasionally, one of the tests timeouts. Inexplicably.

See curl issue 13350

CURLOPT_CONNECT_TO does not work for HTTPS proxy

It is unclear if the same option should even cover the proxy connection or if it requires a separate option.

See curl issue 14481

WinIDN test failures

Test 165 disabled when built with WinIDN.

setting a disabled option should return CURLE_NOT_BUILT_IN

When curl has been built with specific features or protocols disabled, setting such options with curl_easy_setopt() should rather return CURLE_NOT_BUILT_IN instead of CURLE_UNKNOWN_OPTION to signal the difference to the application

See curl issue 15472

LDAP

OpenLDAP hangs after returning results

By configuration defaults, OpenLDAP automatically chase referrals on secondary socket descriptors. The OpenLDAP backend is asynchronous and thus should monitor all socket descriptors involved. Currently, these secondary descriptors are not monitored, causing OpenLDAP library to never receive data from them.

As a temporary workaround, disable referrals chasing by configuration.

The fix is not easy: proper automatic referrals chasing requires a synchronous bind callback and monitoring an arbitrary number of socket descriptors for a single easy handle (currently limited to 5).

Generic LDAP is synchronous: OK.

See curl issue 622 and https://curl.se/mail/lib-2016-01/0101.html

LDAP on Windows does authentication wrong?

curl issue 3116

LDAP on Windows does not work

A simple curl command line getting ldap://ldap.forumsys.com returns an error that says no memory !

curl issue 4261

LDAPS requests to Active Directory server hang

curl issue 9580

TCP/IP

telnet code does not handle partial writes properly

It probably does not happen too easily because of how slow and infrequent sends are normally performed.

Trying local ports fails on Windows

This makes --local-port [range] to not work since curl cannot properly detect if a port is already in use, so it tries the first port, uses that and then subsequently fails anyway if that was actually in use.

curl issue 8112

HTTP/2

HTTP/2 prior knowledge over proxy

curl issue 12641

HTTP/2 frames while in the connection pool kill reuse

If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to curl while the connection is held in curl's connection pool, the socket is found readable when considered for reuse and that makes curl think it is dead and then it is closed and a new connection gets created instead.

This is best fixed by adding monitoring to connections while they are kept in the pool so that pings can be responded to appropriately.

ENHANCE_YOUR_CALM causes infinite retries

Infinite retries with 2 parallel requests on one connection receiving GOAWAY with ENHANCE_YOUR_CALM error code.

See curl issue 5119

HTTP/2 + TLS spends a lot of time in recv

It has been observed that by making the speed limit less accurate we could improve this performance. (by reverting db5c9f4f9e0779) Can we find a golden middle ground?

See https://curl.se/mail/lib-2024-05/0026.html and curl issue 13416

HTTP/3

connection migration does not work

curl issue 7695

quiche: QUIC connection is draining

The transfer ends with error "QUIC connection is draining".

curl issue 12037

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# Known bugs intro
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.
14# TLS
16## IMAPS connection fails with Rustls error
18[curl issue 10457](https://github.com/curl/curl/issues/10457)
20## Access violation sending client cert with Schannel
22When using Schannel to do client certs, curl sets `PKCS12_NO_PERSIST_KEY` to
23avoid leaking the private key into the filesystem. Unfortunately that flag
24instead seems to trigger a crash.
26See [curl issue 17626](https://github.com/curl/curl/issues/17626)
28## Client cert (MTLS) issues with Schannel
30See [curl issue 3145](https://github.com/curl/curl/issues/3145)
32## Schannel TLS 1.2 handshake bug in old Windows versions
34In old versions of Windows such as 7 and 8.1 the Schannel TLS 1.2 handshake
35implementation likely has a bug that can rarely cause the key exchange to
36fail, resulting in error SEC_E_BUFFER_TOO_SMALL or SEC_E_MESSAGE_ALTERED.
38[curl issue 5488](https://github.com/curl/curl/issues/5488)
40## mbedTLS and CURLE_AGAIN handling
42[curl issue 15801](https://github.com/curl/curl/issues/15801)
44## Native CA roots incomplete on Windows with OpenSSL (or fork)
46Certain Windows installations may be missing CA roots.
48[curl issue 20897](https://github.com/curl/curl/issues/20897)
49[curl issue 12303](https://github.com/curl/curl/issues/12303)
51## ECH not working through Proxy Tunnels
53[curl issue 22043](https://github.com/curl/curl/issues/22043)
55# Email protocols
57## IMAP `SEARCH ALL` truncated response
59IMAP `SEARCH ALL` truncates output on large boxes. "A quick search of the code
60reveals that `pingpong.c` contains some truncation code, at line 408, when it
61deems the server response to be too large truncating it to 40 characters"
63https://curl.se/bug/view.cgi?id=1366
65## `AUTH PLAIN` for SMTP is not working on all servers
67Specifying `--login-options AUTH=PLAIN` on the command line does not seem to
68work correctly.
70See [curl issue 4080](https://github.com/curl/curl/issues/4080)
72## `APOP` authentication fails on POP3
74See [curl issue 10073](https://github.com/curl/curl/issues/10073)
76## POP3 issue when reading small chunks
78 CURL_DBG_SOCK_RMAX=4 ./runtests.pl -v 982
80See [curl issue 12063](https://github.com/curl/curl/issues/12063)
82# Command line
84## `-T /dev/stdin` may upload with an incorrect content length
86`-T` stats the path to figure out its size in bytes to use it as
87`Content-Length` if it is a regular file.
89The problem with that is that on BSD and some other UNIX systems (not Linux),
90open(path) may not give you a file descriptor with a 0 offset from the start
91of the file.
93See [curl issue 12177](https://github.com/curl/curl/issues/12177)
95## `-T -` always uploads chunked
97When the `<` shell operator is used. curl should realize that stdin is a
98regular file in this case, and that it can do a non-chunked upload, like it
99would do if you used `-T` file.
101See [curl issue 12171](https://github.com/curl/curl/issues/12171)
103# Build and portability issues
105## OS400 port requires deprecated IBM library
107curl for OS400 requires `QADRT` to build, which provides ASCII wrappers for
108libc/POSIX functions in the ILE, but IBM no longer supports or even offers
109this library to download.
111See [curl issue 5176](https://github.com/curl/curl/issues/5176)
113## `LDFLAGS` passed too late making libs linked incorrectly
115Compiling latest curl on HP-UX and linking against a custom OpenSSL (which is
116on the default loader/linker path), fails because the generated Makefile has
117`LDFLAGS` passed on after `LIBS`.
119See [curl issue 14893](https://github.com/curl/curl/issues/14893)
121## Cygwin: make install installs curl-config.1 twice
123[curl issue 8839](https://github.com/curl/curl/issues/8839)
125## flaky CI builds
127We run many CI builds for each commit and PR on GitHub, and especially a
128number of the Windows builds are flaky. This means that we rarely get all CI
129builds go green and complete without errors. This is unfortunate as it makes
130us sometimes miss actual build problems and it is surprising to newcomers to
131the project who (rightfully) do not expect this.
133See [curl issue 6972](https://github.com/curl/curl/issues/6972)
135## long paths are not fully supported on Windows
137curl on Windows cannot access long paths (paths longer than 260 characters).
138As a workaround, the Windows path prefix `\\?\` which disables all path
139interpretation may work to allow curl to access the path. For example:
140`\\?\c:\longpath`.
142See [curl issue 8361](https://github.com/curl/curl/issues/8361)
144## Unicode on Windows
146Passing in a Unicode filename with -o:
148[curl issue 11461](https://github.com/curl/curl/issues/11461)
150Passing in Unicode character with -d:
152[curl issue 12231](https://github.com/curl/curl/issues/12231)
154Windows Unicode builds use the home directory in current locale.
156The Windows Unicode builds of curl use the current locale, but expect Unicode
157UTF-8 encoded paths for internal use such as open, access and stat. The user's
158home directory is retrieved via curl_getenv in the current locale and not as
159UTF-8 encoded Unicode.
161See [curl pull request 7252](https://github.com/curl/curl/pull/7252) and [curl pull request 7281](https://github.com/curl/curl/pull/7281)
163Cannot handle Unicode arguments in non-Unicode builds on Windows
165If a URL or filename cannot be encoded using the user's current code page then
166it can only be encoded properly in the Unicode character set. Windows uses
167UTF-16 encoding for Unicode and stores it in wide characters, however curl and
168libcurl are not equipped for that at the moment except when built with
169_UNICODE and UNICODE defined. Except for Cygwin, Windows cannot use UTF-8 as a
170locale.
172https://curl.se/bug/?i=345
173https://curl.se/bug/?i=731
174https://curl.se/bug/?i=3747
176The Schannel version verified to work as mentioned in
177https://curl.se/mail/lib-2012-07/0073.html
179# Authentication
181## `--aws-sigv4` signs an empty payload hash for bodies not held in memory
183`--aws-sigv4` hashes only the in-memory POST fields when it computes the payload hash, so a request
184whose body comes from anywhere else is signed as if it had no body at all: the signature is
185computed over `SHA256("")` while a different body goes on the wire. This affects `-F`
186(multipart/form-data) and `-T` (PUT upload) alike.
188`aws:amz:<region>:s3` is not affected, because it sends and signs `UNSIGNED-PAYLOAD` instead. Every
189other service gets the empty hash, with no `x-amz-content-sha256` header sent, and no warning.
191[curl issue 13351](https://github.com/curl/curl/issues/13351)
193## Digest `auth-int` for PUT/POST
195We do not support auth-int for Digest using PUT or POST
197## Digest does not care for `domain`
199libcurl ignores the `domain` directive in Digest authentication challenges
200(`WWW-Authenticate:`). RFC 7616 defines it as a quoted, space-separated list
201of URIs that define the protection space.
203## MIT Kerberos for Windows build
205libcurl fails to build with MIT Kerberos for Windows (`KfW`) due to its
206library header files exporting symbols/macros that should be kept private to
207the library.
209## libcurl can fail to try alternatives with `--proxy-any`
211When connecting via a proxy using `--proxy-any`, a failure to establish an
212authentication causes libcurl to abort trying other options if the failed
213method has a higher preference than the alternatives. As an example,
214`--proxy-any` against a proxy which advertise Negotiate and something else,
215but which fails to set up Kerberos authentication does not proceed to try
216authentication using the other auth method.
218[curl issue 876](https://github.com/curl/curl/issues/876)
220## Do not clear digest for single realm
222[curl issue 3267](https://github.com/curl/curl/issues/3267)
224## SHA-256 digest not supported in Windows SSPI builds
226Windows builds of curl that have SSPI enabled use the native Windows API calls
227to create authentication strings. The call to `InitializeSecurityContext` fails
228with `SEC_E_QOP_NOT_SUPPORTED` which causes curl to fail with
229`CURLE_AUTH_ERROR`.
231Microsoft does not document supported digest algorithms and that `SEC_E` error
232code is not a documented error for `InitializeSecurityContext` (digest).
234[curl issue 6302](https://github.com/curl/curl/issues/6302)
236# FTP
238## FTP with ACCT
240When doing an operation over FTP that requires the `ACCT` command (but not when
241logging in), the operation fails since libcurl does not detect this and thus
242fails to issue the correct command: https://curl.se/bug/view.cgi?id=635
244## FTPS server compatibility on Windows with Schannel
246FTPS is not widely used with the Schannel TLS backend and so there may be more
247bugs compared to other TLS backends such as OpenSSL. In the past users have
248reported hanging and failed connections. It is likely some changes to curl
249since then fixed the issues. None of the reported issues can be reproduced any
250longer.
252If you encounter an issue connecting to your server via FTPS with the latest
253curl and Schannel then please search for open issues or file a new issue.
255# SFTP and SCP
257## SFTP does not do `CURLOPT_POSTQUOTE` correct
259When libcurl sends `CURLOPT_POSTQUOTE` commands when connected to an SFTP
260server using the multi interface, the commands are not being sent correctly
261and instead the connection is canceled (the operation is considered done)
262prematurely. There is a half-baked (busy-looping) patch provided in the bug
263report but it cannot be accepted as-is. See
264https://curl.se/bug/view.cgi?id=748
266## Remote recursive folder creation with SFTP
268On this servers, the curl fails to create directories on the remote server
269even when the `CURLOPT_FTP_CREATE_MISSING_DIRS` option is set.
271See [curl issue 5204](https://github.com/curl/curl/issues/5204)
273## libssh blocking and infinite loop problem
275In the `SSH_SFTP_INIT` state for libssh, the ssh session working mode is set
276to blocking mode. If the network is suddenly disconnected during sftp
277transmission, curl is stuck, even if curl is configured with a timeout.
279[curl issue 8632](https://github.com/curl/curl/issues/8632)
281## Cygwin: "WARNING: UNPROTECTED PRIVATE KEY FILE!"
283Running SCP and SFTP tests on Cygwin makes this warning message appear.
285[curl issue 11244](https://github.com/curl/curl/issues/11244)
287# Connection
289## `--interface` with link-scoped IPv6 address
291When you give the `--interface` option telling curl to use a specific
292interface for its outgoing traffic in combination with an IPv6 address in the
293URL that uses a link-local scope, curl might pick the wrong address from the
294named interface and the subsequent transfer fails.
296Example command line:
298 curl --interface eth0 'http://[fe80:928d:xxff:fexx:xxxx]/'
300The fact that the given IP address is link-scoped should probably be used as
301input to somehow make curl make a better choice for this.
303[curl issue 14782](https://github.com/curl/curl/issues/14782)
305## Does not acknowledge getaddrinfo sorting policy
307Even if a user edits `/etc/gai.conf` to prefer IPv4, curl still prefers and
308tries IPv6 addresses first.
310[curl issue 16718](https://github.com/curl/curl/issues/16718)
312## SOCKS-SSPI discards the security context
314After a successful SSPI/GSS-API exchange, the function queries and logs the
315authenticated username and reports the supported data-protection level, but
316then immediately deletes the negotiated SSPI security context and frees the
317credentials before returning. The negotiated context is not stored on the
318connection and is therefore never used to protect later SOCKS5 traffic.
320## cannot use absolute Unix domain filename for SOCKS on Windows
322curl supports using a Unix domain socket path for speaking SOCKS to a proxy,
323by providing a filename in the URL used for `-x` (`CURLOPT_PROXY`), but that
324path cannot be a proper absolute Windows path with a drive letter etc.
326A solution for this probably requires that we add and provide a
327`--unix-socket` (`CURLOPT_UNIX_SOCKET_PATH`) option alternative for proxy
328communication.
330See [curl issue 19825](https://github.com/curl/curl/issues/19825)
332# Internals
334## GSSAPI library name + version is missing in `curl_version_info()`
336The struct needs to be expanded and code added to store this info.
338See [curl issue 13492](https://github.com/curl/curl/issues/13492)
340## HTTP test server 'connection-monitor' problems
342The `connection-monitor` feature of the HTTP test server does not work
343properly if some tests are run in unexpected order. Like 1509 and then 1525.
345See [curl issue 868](https://github.com/curl/curl/issues/868)
347## Connection information when using TCP Fast Open
349`CURLINFO_LOCAL_PORT` (and possibly a few other) fails when TCP Fast Open is
350enabled.
352See [curl issue 1332](https://github.com/curl/curl/issues/1332) and
353[curl issue 4296](https://github.com/curl/curl/issues/4296)
355## test cases sometimes timeout
357Occasionally, one of the tests timeouts. Inexplicably.
359See [curl issue 13350](https://github.com/curl/curl/issues/13350)
361## `CURLOPT_CONNECT_TO` does not work for HTTPS proxy
363It is unclear if the same option should even cover the proxy connection or if
364it requires a separate option.
366See [curl issue 14481](https://github.com/curl/curl/issues/14481)
368## WinIDN test failures
370Test 165 disabled when built with WinIDN.
372## setting a disabled option should return `CURLE_NOT_BUILT_IN`
374When curl has been built with specific features or protocols disabled, setting
375such options with `curl_easy_setopt()` should rather return
376`CURLE_NOT_BUILT_IN` instead of `CURLE_UNKNOWN_OPTION` to signal the
377difference to the application
379See [curl issue 15472](https://github.com/curl/curl/issues/15472)
381# LDAP
383## OpenLDAP hangs after returning results
385By configuration defaults, OpenLDAP automatically chase referrals on secondary
386socket descriptors. The OpenLDAP backend is asynchronous and thus should
387monitor all socket descriptors involved. Currently, these secondary
388descriptors are not monitored, causing OpenLDAP library to never receive data
389from them.
391As a temporary workaround, disable referrals chasing by configuration.
393The fix is not easy: proper automatic referrals chasing requires a synchronous
394bind callback and monitoring an arbitrary number of socket descriptors for a
395single easy handle (currently limited to 5).
397Generic LDAP is synchronous: OK.
399See [curl issue 622](https://github.com/curl/curl/issues/622) and
400https://curl.se/mail/lib-2016-01/0101.html
402## LDAP on Windows does authentication wrong?
404[curl issue 3116](https://github.com/curl/curl/issues/3116)
406## LDAP on Windows does not work
408A simple curl command line getting `ldap://ldap.forumsys.com` returns an error
409that says `no memory` !
411[curl issue 4261](https://github.com/curl/curl/issues/4261)
413## LDAPS requests to Active Directory server hang
415[curl issue 9580](https://github.com/curl/curl/issues/9580)
417# TCP/IP
419## telnet code does not handle partial writes properly
421It probably does not happen too easily because of how slow and infrequent
422sends are normally performed.
424## Trying local ports fails on Windows
426This makes `--local-port [range]` to not work since curl cannot properly
427detect if a port is already in use, so it tries the first port, uses that and
428then subsequently fails anyway if that was actually in use.
430[curl issue 8112](https://github.com/curl/curl/issues/8112)
432# HTTP/2
434## HTTP/2 prior knowledge over proxy
436[curl issue 12641](https://github.com/curl/curl/issues/12641)
438## HTTP/2 frames while in the connection pool kill reuse
440If the server sends HTTP/2 frames (like for example an HTTP/2 PING frame) to
441curl while the connection is held in curl's connection pool, the socket is
442found readable when considered for reuse and that makes curl think it is dead
443and then it is closed and a new connection gets created instead.
445This is *best* fixed by adding monitoring to connections while they are kept
446in the pool so that pings can be responded to appropriately.
448## `ENHANCE_YOUR_CALM` causes infinite retries
450Infinite retries with 2 parallel requests on one connection receiving `GOAWAY`
451with `ENHANCE_YOUR_CALM` error code.
453See [curl issue 5119](https://github.com/curl/curl/issues/5119)
455## HTTP/2 + TLS spends a lot of time in recv
457It has been observed that by making the speed limit less accurate we could
458improve this performance. (by reverting
459[db5c9f4f9e0779](https://github.com/curl/curl/commit/db5c9f4f9e0779b49624752b135281a0717b277b))
460Can we find a golden middle ground?
462See https://curl.se/mail/lib-2024-05/0026.html and
463[curl issue 13416](https://github.com/curl/curl/issues/13416)
465# HTTP/3
467## connection migration does not work
469[curl issue 7695](https://github.com/curl/curl/issues/7695)
471## quiche: QUIC connection is draining
473The transfer ends with error "QUIC connection is draining".
475[curl issue 12037](https://github.com/curl/curl/issues/12037)
Diagnostics4 git calls · 31 ms
CallStatusSizeTime031 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2007.1 KiB · hit25 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=25
git.response.bytes=7222
git.response.cache=HIT
git.response.duration_ms=25
git.fetch.wants=d2eb817e04cffc1e3e8fd6a73306acb5341dbd4c
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=7222
git.pkt.payload.max=7201
git.sideband.band1.bytes=7200
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e1e5a94820d96e
Request
56e4c55b…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format