Topics   All   Mac OS X (Only)   Windows (Only)   Linux (Only, Not)   iOS (Only, Not)  
Components   Crossplatform Mac & Win   Server (Not)   Client   Old   Guides   Examples
New in version: 6.4   6.5   7.0   7.1   7.2   7.3   7.4   7.5   8.0   8.1    Statistic  


Which command to use for reaching a file.

Component Version macOS Windows Server FileMaker Cloud FileMaker iOS SDK
CURL 2.5 Yes Yes Yes Yes Yes

MBS( "CURL.SetOptionFTPFileMethod"; Handle; Value )


Parameter Description Example value
Handle The CURL session handle. $curl
Value Which CWD command to use. 0


Returns "OK" on success.


Which command to use for reaching a file.
Pass a long that should have one of the following values. This option controls what method libcurl should use to reach a file on a FTP(S) server. The argument should be one of the following alternatives:

Multi CWD1libcurl does a single CWD operation for each path part in the given URL. For deep hierarchies this means many commands. This is how RFC 1738 says it should be done. This is the default but the slowest behavior.
No CWD2libcurl does no CWD at all. libcurl will do SIZE, RETR, STOR etc and give a full path to the server for all these commands. This is the fastest behavior.
Single CWD3libcurl does one CWD with the full target directory and then operates on the file "normally" (like in the multicwd case). This is somewhat more standards compliant than 'nocwd' but without the full penalty of 'multicwd'.


Use single CWD command:

MBS( "CURL.SetOptionFTPFileMethod"; $curl; 3 )

CURL.SetOptionFTPCreateMissingDirs   -   CURL.SetOptionFTPPort

Feedback: Report problem or ask question.

MBS Xojo tutorial videos