diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2016-04-05 23:39:42 +0200 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2016-04-05 23:39:42 +0200 |
| commit | 52b3e072f63a8e5220767cdb292a204ec3750838 (patch) | |
| tree | 737d76f3d6e4613b67f025aa8649e92e1ba53688 /docs/KNOWN_BUGS | |
| parent | c8ab61312cb913232a7b3874bdcafa215d6b21db (diff) | |
KNOWN_BUGS: remove 92 and 88, fixed
Diffstat (limited to 'docs/KNOWN_BUGS')
| -rw-r--r-- | docs/KNOWN_BUGS | 14 |
1 files changed, 0 insertions, 14 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index a694ced05..686fd317a 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -9,17 +9,6 @@ may have been fixed since this was written! purpose char* for storing these values in via casting. For more information see the now closed related issue: https://github.com/curl/curl/issues/608 - -92. curl tool 7.47.1 in Windows will not --output to literal paths \\?\ or to - reserved dos device names unless the device prefix \\.\ is used. To send - output to a device that has a reserved dos device name you can use the - Windows device prefix (eg: --output \\.\NUL). You can also use the - redirection operator to send output to a literal path or a reserved device - name (eg: > NUL). - The next release of curl will support --output in Windows to literal paths - and to reserved device names without the device prefix. - https://github.com/curl/curl/commit/c3aac48 - https://github.com/curl/curl/commit/4fc80f3 91. "curl_easy_perform hangs with imap and PolarSSL" https://github.com/curl/curl/issues/334 @@ -33,9 +22,6 @@ may have been fixed since this was written! 89. Disabling HTTP Pipelining when there are ongoing transfers can lead to heap corruption and crash. https://curl.haxx.se/bug/view.cgi?id=1411 -88. libcurl doesn't support CURLINFO_FILETIME for SFTP transfers and thus - curl's -R option also doesn't work then. - 87. -J/--remote-header-name doesn't decode %-encoded file names. RFC6266 details how it should be done. The can of worm is basically that we have no charset handling in curl and ascii >=128 is a challenge for us. Not to |