|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #21736 fsockopen timeouts
Submitted: 2003-01-18 16:36 UTC Modified: 2003-02-04 16:50 UTC
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:1 (50.0%)
From: support at websiteout dot net Assigned:
Status: No Feedback Package: Sockets related
PHP Version: 4.3.1-dev OS: Linux (kernel 2.4.18)
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
5 - 1 = ?
Subscribe to this entry?

 [2003-01-18 16:36 UTC] support at websiteout dot net

PHP4.3.0 is a great version. Congratulations.
Just on thing about fsockopen()
Let's try this simple script :
echo fsockopen("", 80);
It works fine in PHP4.2.x but it timeouts in PHP4.3.0
Thanks a lot


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2003-01-18 18:17 UTC]
Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at

If you can provide more information, feel free to add it
to this bug and change the status back to "Open".

Thank you for your interest in PHP.

What times out?  The script or the fsockopen call?
What is the error message?

*please* read the info here:
and then fill in more information to make this a useful bug report.
 [2003-01-18 19:45 UTC] support at websiteout dot net
Thanks for your answer.
You're right, it is not the fsockopen() which times out. It is the script itself because the fsockopen() never responds.
After 1 minute waiting for a respond, my browser give up.
So I don't have any error message from the script.

Here is some hints:
- the script runs fine on PHP4.2.x but not on PHP4.3.0
- fsockopen("", 80); works fine on both PHP4.3.0 and PHP4.2.x
- fsockopen("", 80); also works fine on both PHP4.3.0 and PHP4.2.x
- if you need, you can find the phpinfo page at this address :

Thans a lot.
 [2003-01-19 03:44 UTC]
And did you read the NEWS for PHP 4.3.0?

"Added php.ini option "default_socket_timeout" to set the
timeout limit for PHP network streams.
(kalowsky,, Wez)"

This setting is documented here:

Changing this to a documentation problem as the fsockopen page should mention this new feature (which helps prevents potential DOS attacks), and the documentation of the ini setting should be listed in either the network functions summary or in the new streams section.
 [2003-01-19 03:48 UTC]
Please try using this CVS snapshot:
For Windows:

sorry - I just re-read you report (it's early!).
Can you try a stable snapshot?
If it still hangs, can you read the instructions here:
and follow the "If you can't get a core file" section;
when/if php hangs (after approx 1 minute), interrupt the httpd by pressing CTRL-C and then type "bt full".

 [2003-01-19 03:53 UTC]
I stand by my original comment; you have your max_execution_time set to 30 seconds, while the default_socket_timeout is 60 seconds.
Try setting it to something less than 30 seconds (or even using the timeout parameter to fsockopen).
 [2003-01-19 09:45 UTC] support at websiteout dot net

We have set default_socket_timeout=20
It changes nothing. 
fsockopen() doesn't respond even after 20 secs.
After 1 minute waiting for a respond, my browser give up.
So I don't have any error message from the script.
Again, it works fine in PHP4.2.x. It responds (positively) in less than 3 secs and the socket is correctly open.
Tonight I will try with
I will tell you what happens.

 [2003-01-19 18:28 UTC]
leaving marked as feedback until user reports back.
 [2003-01-19 18:34 UTC] support at websiteout dot net

I just tried :
and the problem remains the same.

I'm sorry to bore you with that.
 [2003-01-19 23:57 UTC]
FYI: I can NOT reproduce this with PHP 4.3.1-dev.

 [2003-01-20 05:20 UTC] support at websiteout dot net
Don't worry so. I will ask to my developpers to look in fsock.c to correct the problem.
You can close the bug if you want.
Have a good day.
 [2003-01-20 09:04 UTC]
Please try generating a backtrace as I asked, otherwise we will never know what is causing this problem.
 [2003-02-04 16:50 UTC]
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-2024 The PHP Group
All rights reserved.
Last updated: Fri Jul 19 03:01:27 2024 UTC