aboutsummaryrefslogtreecommitdiff
path: root/docs/TODO
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2002-02-18 10:51:28 +0000
committerDaniel Stenberg <daniel@haxx.se>2002-02-18 10:51:28 +0000
commit5c4b422b180b1b8ef104510f633e5be2e5127ab5 (patch)
treec73e38752940bcc2459d844c48e6ddf70729f39e /docs/TODO
parent89bad584c38a681642d100c789ba6c3391988237 (diff)
offer SSL verfication callback,
add 'headers=' in client formpost
Diffstat (limited to 'docs/TODO')
-rw-r--r--docs/TODO21
1 files changed, 19 insertions, 2 deletions
diff --git a/docs/TODO b/docs/TODO
index 367c46a03..1dd749d05 100644
--- a/docs/TODO
+++ b/docs/TODO
@@ -49,8 +49,8 @@ TODO
very long time idle connections.
* Make sure we don't ever loop because of non-blocking sockets return
- EWOULDBLOCK or similar. This concerns the HTTP request sending, the FTP
- command sending etc.
+ EWOULDBLOCK or similar. This concerns the HTTP request sending (and
+ especially regular HTTP POST), the FTP command sending etc.
* Go through the code and verify that libcurl deals with big files >2GB and
>4GB all over. Bug reports indicate that it doesn't currently work
@@ -143,6 +143,11 @@ TODO
idea might become moot if we enable the 'data sharing' as mentioned in the
LIBCURL label above.
+ * OpenSSL supports a callback for customised verification of the peer
+ certificate, but this doesn't seem to be exposed in the libcurl APIs. Could
+ it be? There's so much that could be done if it were! (brought by Chris
+ Clark)
+
* Make curl's SSL layer option capable of using other free SSL libraries.
Such as the Mozilla Security Services
(http://www.mozilla.org/projects/security/pki/nss/) and GNUTLS
@@ -167,6 +172,18 @@ TODO
make sure that happens. It should of course not make more than one
connection to the same remote host.
+ * Extending the capabilities of the multipart formposting. How about leaving
+ the ';type=foo' syntax as it is and adding an extra tag (headers) which
+ works like this: curl -F "coolfiles=@fil1.txt;headers=@fil1.hdr" where
+ fil1.hdr contains extra headers like
+
+ Content-Type: text/plain; charset=KOI8-R"
+ Content-Transfer-Encoding: base64
+ X-User-Comment: Please don't use browser specific HTML code
+
+ which should overwrite the program reasonable defaults (plain/text,
+ 8bit...) (Idea brough to us by kromJx)
+
TEST SUITE
* Extend the test suite to include more protocols. The telnet could just do