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 — Включает или выключает пассивный режим
ftp_pasv() включает или выключает пассивный режим. В пассивном режиме передача данных инициируется клиентом, а не сервером. Данный режим может понадобиться в случае, если клиент находится за брандмауэром.
Обратите внимание, что ftp_pasv() может быть вызвана только после успешной авторизации, иначе она завершится с ошибкой.
ftp
An FTP\Connection instance.
enable
Если true
, пассивный режим будет включён, иначе выключен.
Возвращает true
в случае успешного выполнения или false
в случае возникновения ошибки.
Версия | Описание |
---|---|
8.1.0 |
Параметр ftp теперь ожидает экземпляр FTP\Connection;
ранее ожидался ресурс (resource).
|
Пример #1 Пример использования ftp_pasv()
<?php
$file = 'somefile.txt';
$remote_file = 'readme.txt';
// установка соединения
$conn_id = ftp_connect($ftp_server);
// проверка имени пользователя и пароля
$login_result = ftp_login($conn_id, $ftp_user_name, $ftp_user_pass);
// включение пассивного режима
ftp_pasv($conn_id, true);
// загрузка файла
if (ftp_put($conn_id, $remote_file, $file, FTP_ASCII)) {
echo "$file успешно загружен на сервер\n";
} else {
echo "Не удалось загрузить $file на сервер\n";
}
// закрытие соединения
ftp_close($conn_id);
?>
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...
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 ;)
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);
?>
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.)
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.