Loading docs/TODO +2 −12 Original line number Diff line number Diff line Loading @@ -62,24 +62,14 @@ TODO FTP * "PASV IP override" - When an FTPS host is behind a NAT firewall, passive mode fails. The PASV response from the host ["227 PASV Entering passive mode (_ip_address_, _port_)."] contains the private network IP address of the host, which since it is encrypted, cannot be modified by the firewall to the public IP address. What is needed is a cURL option to override the IP address passed by the host "227 PASV" response. Requested by Ed Hingsbergen * Support GSS/Kerberos 5 for ftp file transfer. This will allow user authentication and file encryption. Possible libraries and example clients are available from MIT or Heimdal. Requsted by Markus Moeller. * Optimize the way libcurl uses CWD on each new request over a persistent connection (on FTP) even if it doesn't have to. * REST fix for servers not behaving well on >2GB requests. This should fail if the server doesn't set the pointer to the requested index. The tricky part is to figure out if the server did the right thing or not. (impossible?) part is to figure out if the server did the right thing or not. * Support the most common FTP proxies, Philip Newton provided a list allegedly from ncftp: Loading Loading
docs/TODO +2 −12 Original line number Diff line number Diff line Loading @@ -62,24 +62,14 @@ TODO FTP * "PASV IP override" - When an FTPS host is behind a NAT firewall, passive mode fails. The PASV response from the host ["227 PASV Entering passive mode (_ip_address_, _port_)."] contains the private network IP address of the host, which since it is encrypted, cannot be modified by the firewall to the public IP address. What is needed is a cURL option to override the IP address passed by the host "227 PASV" response. Requested by Ed Hingsbergen * Support GSS/Kerberos 5 for ftp file transfer. This will allow user authentication and file encryption. Possible libraries and example clients are available from MIT or Heimdal. Requsted by Markus Moeller. * Optimize the way libcurl uses CWD on each new request over a persistent connection (on FTP) even if it doesn't have to. * REST fix for servers not behaving well on >2GB requests. This should fail if the server doesn't set the pointer to the requested index. The tricky part is to figure out if the server did the right thing or not. (impossible?) part is to figure out if the server did the right thing or not. * Support the most common FTP proxies, Philip Newton provided a list allegedly from ncftp: Loading