1
0
mirror of https://github.com/moparisthebest/curl synced 2024-10-31 15:45:12 -04:00

Added: 4 protocols we _could_ support and the CONNECT HTTP/1.0 detail we might

fix one day.
This commit is contained in:
Daniel Stenberg 2004-12-22 09:19:29 +00:00
parent 8b5f0abef1
commit 2910880b15

View File

@ -99,6 +99,10 @@ TODO
This could possibly be implemented using the multi interface to queue This could possibly be implemented using the multi interface to queue
requests and the response data. requests and the response data.
* When doing CONNECT to a HTTP proxy, libcurl always uses HTTP/1.0. This has
never been reported as causing trouble to anyone, but should be considered
to use the HTTP version the user has chosen.
TELNET TELNET
* Reading input (to send to the remote server) on stdin is a crappy solution * Reading input (to send to the remote server) on stdin is a crappy solution
@ -151,6 +155,22 @@ TODO
lib/ldap.c source file and get moved to the main network code so that the lib/ldap.c source file and get moved to the main network code so that the
multi interface and friends will work for LDAP as well. multi interface and friends will work for LDAP as well.
NEW PROTOCOLS
* TFTP - RFC1350 (protocol) and RFC3617 (URI format)
Dan Fandrich: I wrote a tftp protocol module as part of the I-Boot
bootloader under a BSD-style license with attribution clause
http://download.intrinsyc.com/supported/tools/i-boot-lite/i-boot-lite-1.8/src/libs/net/tftp.c
* RTSP - RFC2326 (protocol - very HTTP-like, also contains URL description)
* SFTP/SCP/SSH (no RFCs for protocol nor URI/URL format). An implementation
should most probably use an existing ssh library, such as OpenSSH.
* RSYNC (no RFCs for protocol nor URI/URL format). An implementation should
most probably use an existing ssh library, such as librsync.
CLIENT CLIENT
* "curl --sync http://example.com/feed[1-100].rss" or * "curl --sync http://example.com/feed[1-100].rss" or