http://stackoverflow.com/questions/16026619/when-to-use-ftp-pasv
Khi code ftp PHP thuần, mới đầu dùng server test m tự build máy ảo ubuntu thì ok.
Sau chạy sv thật thì ko list đc data => Cuối cùng set ftp_pasv($conn_id, true); thì đc.
Sau 1 tg có vẻ sv lại đổi setting j đó nên phải bỏ (comment) pasv mode đi mới lấy đc data.
Chưa rõ nguyên nhân chính xác với cách handle cả 2 mode. Khả năng 1 số lib có handle case này ?
Ko thì handle = tay; lấy thông tin FTP server bắn về để xác định mode support ?
Some answers here:
http://www.elitehosts.com/blog/php-ftp-passive-ftp-server-behind-nat-nightmare/
http://stackoverflow.com/questions/1699145/what-is-the-difference-between-active-and-passive-ftp
Active and passive are the two modes that FTP can run in. FTP uses two channels between client and server, the command channel and the data channel, which are actually separate TCP connections. The command channel is for commands and responses, the data channel is for actually transferring files. It's a nifty way of sending commands to the server without having to wait for the current data transfer to finish.
In active mode, the client establishes the command channel (from client port X to server port 21(b)) but the server establishes the data channel (from server port 20(b) to client port Y, where Y has been supplied by the client).
In passive mode, the client establishes both channels. In that case, the server tells the client which port should be used for the data channel.
Passive mode is generally used in situations where the FTP server is not able to establish the data channel. One of the major reasons for this is network firewalls. While you may have a firewall rule which allows you to open up FTP channels to ftp.microsoft.com, Microsoft's servers may not have the power to open up the data channel back through your firewall.
Passive mode solves this by opening up both types of channel from the client side. In order to make this hopefully clearer:
Active mode:
Client opens up command channel from client port 2000(a) to server port 21(b).
Client sends PORT 2001(a) to server and server acknowledges on command channel.
Server opens up data channel from server port 20(b) to client port 2001(a).
Client acknowledges on data channel.
Passive mode:
Client opens up command channel from client port 2000(a) to server port 21(b).
Client sends PASV to server on command channel.
Server sends back (on command channel) PORT 1234(a) after starting to listen on that port.
Client opens up data channel from client 2001(a) to server port 1234(a).
Server acknowledges on data channel.
At this point, the command and data channels are both open.
(a)Note that the selection of ports on the client side is up to the client, as the selection of the server data channel port in passive mode is up to the server.
(b)Further note that the use of port 20 and 21 is only a convention (although a strong one). There's no absolute requirement that those ports be used although the client and server both have to agree on which ports are being used. I've seen implementations that try to hide from clients by using different ports (futile, in my opinion).
Khi code ftp PHP thuần, mới đầu dùng server test m tự build máy ảo ubuntu thì ok.
Sau chạy sv thật thì ko list đc data => Cuối cùng set ftp_pasv($conn_id, true); thì đc.
Sau 1 tg có vẻ sv lại đổi setting j đó nên phải bỏ (comment) pasv mode đi mới lấy đc data.
Chưa rõ nguyên nhân chính xác với cách handle cả 2 mode. Khả năng 1 số lib có handle case này ?
Ko thì handle = tay; lấy thông tin FTP server bắn về để xác định mode support ?
Some answers here:
http://www.elitehosts.com/blog/php-ftp-passive-ftp-server-behind-nat-nightmare/
http://stackoverflow.com/questions/1699145/what-is-the-difference-between-active-and-passive-ftp
Active and passive are the two modes that FTP can run in. FTP uses two channels between client and server, the command channel and the data channel, which are actually separate TCP connections. The command channel is for commands and responses, the data channel is for actually transferring files. It's a nifty way of sending commands to the server without having to wait for the current data transfer to finish.
In active mode, the client establishes the command channel (from client port X to server port 21(b)) but the server establishes the data channel (from server port 20(b) to client port Y, where Y has been supplied by the client).
In passive mode, the client establishes both channels. In that case, the server tells the client which port should be used for the data channel.
Passive mode is generally used in situations where the FTP server is not able to establish the data channel. One of the major reasons for this is network firewalls. While you may have a firewall rule which allows you to open up FTP channels to ftp.microsoft.com, Microsoft's servers may not have the power to open up the data channel back through your firewall.
Passive mode solves this by opening up both types of channel from the client side. In order to make this hopefully clearer:
Active mode:
Client opens up command channel from client port 2000(a) to server port 21(b).
Client sends PORT 2001(a) to server and server acknowledges on command channel.
Server opens up data channel from server port 20(b) to client port 2001(a).
Client acknowledges on data channel.
Passive mode:
Client opens up command channel from client port 2000(a) to server port 21(b).
Client sends PASV to server on command channel.
Server sends back (on command channel) PORT 1234(a) after starting to listen on that port.
Client opens up data channel from client 2001(a) to server port 1234(a).
Server acknowledges on data channel.
At this point, the command and data channels are both open.
(a)Note that the selection of ports on the client side is up to the client, as the selection of the server data channel port in passive mode is up to the server.
(b)Further note that the use of port 20 and 21 is only a convention (although a strong one). There's no absolute requirement that those ports be used although the client and server both have to agree on which ports are being used. I've seen implementations that try to hide from clients by using different ports (futile, in my opinion).
Comments
Post a Comment