Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip

I used the latest snapshot.  fgets() still hangs on that specific url and stream_set_timeout does not time out.  It should return false but doesn't.

I suspect the problem to be with feof() rather than fgets().

try this:

do {
   $line = fgets($fp);
   if ($line === false)
      break;
   $html .= trim($line);
} while(true);

The url is now working now so I cannot use it as a test case (it needs to return false).  I will see if I can find a new url to test it with the new code.

So the URL needs to return a failure code in order
to trigger the problem?
Please as specific as you can about it to help us figure
out whats happening.

I think removing feof() solved the problem.  I don't get any infinite stalls anymore.  Thanks.

I will try to answer the question the best I can.

I have written a spider in php that can index millions of pages.  Every once in a while it will encounter a page that will not load up (which I thought was due to fgets).  When I type this url in the location bar of a browser, the page seems like it will load forever and nothing will show up.

When I set stream_set_timeout($fd, 6) then once would expect that $fd will time out in 6 seconds and exit the loop.  I believe that feof would detect that the stream would time out:


if ($fd = @fopen($url,'rb')){
   stream_set_timeout($fd, 6);
   $html = '';
   while (!feof($fd)) {
      $html .= trim(fgets($fd));
   }
   fclose($fd);
}

To answer wez's question, I had to find a url that didn't work (that took forever to load) in order to test that feof would exit due to the timing out of the stream ($fd).

The url that I was using wasn't working for about one day.  Then it started to load normally in a browser a day later so I couldn't use it anymore as a test case for this problem.

Making the stream time out is important for my application because it needs to move on to the next url or else it will loop forever.

Hope that helps.

If you have a server which is under extreme load and is taking around 30 seconds to respond, results similar to a DoS attack. It appears that the stream doesn't have a timeout so it simply finishes when max_execution_time is reached.

Please try using this CVS snapshot:

  http://snaps.php.net/php4-STABLE-latest.tar.gz
 
For Windows:
 
  http://snaps.php.net/win32/php4-win32-STABLE-latest.zip

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.

Guys, looks like server just tries to keep connection alive. To avoid this put "Connection: close" onto your http header.