It should be noted that ftp_pasv has to be called AFTER ftp_login (not after ftp_connect). May seem obvious to many but it took me three hours to find out...
(PHP 4, PHP 5, PHP 7, PHP 8)
ftp_pasv — Active ou désactive le mode passif
ftp_pasv() active ou non le mode passif. En mode passif, les données de connexion sont initiées par le client, plutôt que par le serveur. Ce mode peut être nécessaire lorsque le client est derrière un pare-feu.
Notez que ftp_pasv() ne peut être appelée qu'après une identification réussie, sinon, la fonction échouera.
ftp
Une instance de FTP\Connection.
enable
Si true
, le mode passif est activé, sinon, il est désactivé.
Version | Description |
---|---|
8.1.0 |
La paramètre ftp attend désormais une instance de
FTP\Connection ; auparavant, une resource était attendu.
|
Exemple #1 Exemple avec ftp_pasv()
<?php
$file = 'somefile.txt';
$remote_file = 'readme.txt';
// Mise en place d'une connexion basique
$ftp = ftp_connect($ftp_server);
// Identification avec un nom d'utilisateur et un mot de passe
$login_result = ftp_login($ftp, $ftp_user_name, $ftp_user_pass);
// Activation du mode passif
ftp_pasv($ftp, true);
// Chargement d'un fichier
if (ftp_put($ftp, $remote_file, $file, FTP_ASCII)) {
echo "Le fichier $file a été chargé avec succès\n";
} else {
echo "Il y a eu un problème lors du chargement du fichier $file\n";
}
// Fermeture de la connexion
ftp_close($ftp);
?>
It should be noted that ftp_pasv has to be called AFTER ftp_login (not after ftp_connect). May seem obvious to many but it took me three hours to find out...
For some FTP servers, it seems the sequence of passive and other commands matters more than for other FTP servers. Sorry, I don't know what vendor or version specifically.
<?php
ftp_pasv($handle, true);
echo "System type: ".ftp_systype($handle).PHP_EOL;
ftp_fput($handle, 'example.txt', $stream, FTP_BINARY);
?>
> PHP Warning: ftp_fput(): STOR out of sequence.
<?php
echo "System type: ".ftp_systype($handle).PHP_EOL;
ftp_pasv($handle, true);
ftp_fput($handle, 'example.txt', $stream, FTP_BINARY);
?>
> no issue
If you are running filezilla in passive mode, on windows, and try to connect using PHP, you might encounter an error that reads "425 Can't open data connection for transfer of ..."
This error is not indicative of a passive mode issue, but can be resolved by using
<?php
ftp_pasv($conn, true);
?>
If you are still having problems after choosing ftp_pasv() you should refresh the connection through ftp_close() / ftp_connect() after x files and/or y GB have been transfered.
It solved several (random) occurring problems like:
ftp_get(): Opening BINARY mode data connection
ftp_get(): Entering Passive Mode
Hint: fopen() created a file so don't forget to delete it if an error occurred ;)
PASV: For ftp users behind firewall, the server LISTEN for a connection.
Non-PASV: The client LISTEN for a connection from server.
If you find that you are receiving "Illegal PORT command" errors you may want to try enabling passive mode.
I found one place that required passive mode to function properly, but the initial error manifested itself in an odd way:
PHP Warning: ftp_put(): TYPE is now ASCII in <file.php> on line <#>
or
PHP Warning: ftp_put(): TYPE is now 8 BIT BINARY in <file.php> on line <#>
The other symptom is that it was taking a long time, perhaps the 90 seconds that the timeout was set to. No errors occurred upon connect, just when I tried ftp_put().
Once I turned on ftp_pasv() it worked, both in the place where active mode worked, and on the server where active mode wouldn't work.
Directly from bsd FTP manual pages:
The PASV command requests that the remote server open a port for the data connection and return the address of that port. The remote server listens on that port and the client connects to it.
When using the more traditional PORT command, the client listens on a port and sends that address to the remote server, who connects back to it. Passive mode is useful when using ftp through a gateway router or host that controls the directionality of traffic. (Note that though ftp servers are required to support the PASV command by RFC 1123, some do not.)