php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #25641 ftp_rawlist long list retrive fail after 60 sec
Submitted: 2003-09-24 05:42 UTC Modified: 2003-09-29 05:55 UTC
From: sentomas at hotmail dot com Assigned:
Status: No Feedback Package: FTP related
PHP Version: 4.3.3 OS: FreeBSD
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: sentomas at hotmail dot com
New email:
PHP Version: OS:

 

 [2003-09-24 05:42 UTC] sentomas at hotmail dot com
Description:
------------
if the ftp list so long that can retrive in 60sec, the ftp_rawlist() automaticly fail. 

I re-set FTP timeout and default_socket timeout and of cause use commandline mode , but it didnt seems to work.



Reproduce code:
---------------
//-lR option in order to make ftp server reply whole dir list, which might be very very long, so its take time more than 60 sec.
$dirlist = ftp_rawlist($conn_id, "-lR");
if ($dirlist === false){
   //defintely fail whatever you do after 60sec
   //commandline mode 
   return "fail";
}

Expected result:
----------------
might be some kind of "default_socket_timeout" limit in inter-core? because i saw the ftp.c will write to the list tmpfile first then output to array.


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2003-09-24 13:32 UTC] pollita@php.net
Your use of ftp_rawlist is incorrect.  The second argument must contain a path (otherwise a -- technicly -- invalid command is sent to the server).

Try again with ftp_rawlist($conn_if, "-lR /");

(Passing -lR as arguments, while undocumented, will at least not result in invalid behavior)

I'm not saying this is necessarily the problem (in fact it's probably not), but I'd like to rule it out.

In the mean time, are you querying a public FTP server?  If so which one? (I'd like to reproduce the precise circumstances).  If it's a private FTP, it would help to at least know what FTP daemon is running (i.e.: ProFTPd, IIS, etc...)


 [2003-09-29 05:55 UTC] sniper@php.net
No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.


 
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Wed Jan 29 08:01:25 2020 UTC