Chilkat Perl FTP Library with FTPS 9.4.1
A unique FTP library for Perl developers
Chilkat Perl FTP Library with FTPS allows you to create FTP and file transfer applications with ease.
Chilkat Perl FTP Library with FTPS is written in the Perl programming language.
- FTP files directly from your application in synchronous or asynchronous mode.
- Support for FTPS - FTP over SSL 3.0 and TLS 1.0
- All popular FTP servers and proxies are supported.
- Resume (restart) FTP uploads and downloads
- Supports international filenames in all major languages
- Upload and download to or from in-memory strings or byte arrays.
- Automatic directory listing parser for FTP servers on Unix, Windows, Netware, AS/400, VAX/VMS, IBM Mainframes, and other legacy formats.
- Session logging
- XCRC verification of uploads and downloads
- Synchronize local directory tree with remote directory tree in either direction
- All asynchronous operations are abortable
- Real-time upload/download data transfer rate properties
- Real-time #bytes received/sent properties for async transfers
- Secure FTP (FTPS) using AUTH TLS
- Implicit Secure FTP SSL on Port 990 (or whichever port is used by the FTP server for SSL/TLS)
- Clear the Control Channel (CCC) after FTPS Authentication
- Supports FTPS behind Network Address Translating (NAT) Routers such as DSL/Cable Modems
- Automatically handles One-Time Password (OTP), also known as S/KEY authentication.
- Delete an entire remote directory tree in a single line of code
- Upload an entire directory tree in a single line of code
- Download an entire remote directory tree in a single line of code
- Copy remote files to your local filesystem.
- Copy files from your local filesystem to the FTP server.
- Download text and binary files and access directly in memory.
- Upload to FTP site directly from memory.
- Create remote directory.
- Rename remote files and directories.
- Delete remote files and directories.
- Get remote directory listing as XML.
- Support for asynchronous uploads and downloads.
- Active and passive transfer modes.
- Binary and ASCII transfers.
- FTP proxy servers are supported.
- SOCKS4/SOCKS5 proxy support.
- Server specific commands supported (SITE command) - such as setting access permissions on Unix FTP servers.
- Stream support - streaming download to local files, streaming upload from local files.
- Large file support - upload or download files larger than 4 GB.
- Auto-determine proxy settings
- Auto-determine valid connection settings
- Specify port range for PORT mode data transfers (i.e. Active mode).
- Supports QUOTE and SYST
- Allows for client SSL certificate to be used for SSL connections.
- Provides access to FTP SSL server certificate for verification.
- Unlimited one-year phone and email support.
- Upgrades are always free
- Royalty-free licensing
- License covers all programming languages: .NET, ActiveX, C++, Ruby, Perl, Python, Java, etc.
Chilkat Perl FTP Library with FTPS
In a hurry? Add it to your Download Basket!
What's New in version 9.4.0
- (backward compatibility) Removed the deprecated CkCrypt and CkFtp C++ classes. (CkCrypt2 and CkFtp2 have been the primary C++ classes for encryption and FTP for many years.)
- (backward compatibility) Removed the deprecated Chilkat.Crypt and Chilkat.Ftp .NET classes. (The primary Chilkat .NET classes for encryption and FTP have been Chilkat.Crypt2 and Chilkat.Ftp2 for many years.)
- (backward compatibility) Removed the “Blacklist” class wherever it may have been present. This class has been deprecated for many years, and the online documentation for it was removed many years ago.
- (backward compatibility, C++ API) All C++ method arguments that were pointers to objects have now become references to objects. For example, if a method argument was “CkCert *”, it is now “CkCert &”. This cause a compilation error, but the coding fix is very simple (just dereference the pointer that is passed). There are two exceptions. One is for CkXml::Search* methods where the 1st argument may be NULL, and therefore the pointer argument (CkXml *) was maintained. The second is for event callback objects (see below).