summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohn E. Malmberg <wb8tyw@qsl.net>2013-08-08 23:34:36 +0200
committerDaniel Stenberg <daniel@haxx.se>2013-08-08 23:34:36 +0200
commit015556d74c27612ea6e26f9a0785248ef81b77bc (patch)
treea4b9fbcfdfbb1944a5bc2cd8772965afa84cd6f6
parent4c40fe64b8f9ea0199fcba2621cabf7057f20b82 (diff)
downloadgnurl-015556d74c27612ea6e26f9a0785248ef81b77bc.tar.gz
gnurl-015556d74c27612ea6e26f9a0785248ef81b77bc.tar.bz2
gnurl-015556d74c27612ea6e26f9a0785248ef81b77bc.zip
KNOWN_BUGS: 22 and 57 have been fixed and committed
-rw-r--r--docs/KNOWN_BUGS13
1 files changed, 0 insertions, 13 deletions
diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS
index 87f186c67..7bd6e6e32 100644
--- a/docs/KNOWN_BUGS
+++ b/docs/KNOWN_BUGS
@@ -104,13 +104,6 @@ may have been fixed since this was written!
CURLOPT_FAILONERROR with FTP to detect if a file exists or not, but it is
not working: http://curl.haxx.se/mail/lib-2008-07/0295.html
-57. On VMS-Alpha: When using an http-file-upload the file is not sent to the
- Server with the correct content-length. Sending a file with 511 or less
- bytes, content-length 512 is used. Sending a file with 513 - 1023 bytes,
- content-length 1024 is used. Files with a length of a multiple of 512 Bytes
- show the correct content-length. Only these files work for upload.
- http://curl.haxx.se/bug/view.cgi?id=2057858
-
56. When libcurl sends CURLOPT_POSTQUOTE commands when connected to a SFTP
server using the multi interface, the commands are not being sent correctly
and instead the connection is "cancelled" (the operation is considered done)
@@ -188,12 +181,6 @@ may have been fixed since this was written!
We probably have even more bugs and lack of features when a SOCKS proxy is
used.
-22. Sending files to a FTP server using curl on VMS, might lead to curl
- complaining on "unaligned file size" on completion. The problem is related
- to VMS file structures and the perceived file sizes stat() returns. A
- possible fix would involve sending a "STRU VMS" command.
- http://curl.haxx.se/bug/view.cgi?id=1156287
-
21. FTP ASCII transfers do not follow RFC959. They don't convert the data
accordingly (not for sending nor for receiving). RFC 959 section 3.1.1.1
clearly describes how this should be done: