Re: fsockopen error messages
| From: | Philip Thompson | Date: | Mon, 06 Nov 2006 21:30:06 +0000 |
| Subject: | Re: fsockopen error messages | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-244279@lists.php.net to get a copy of this message | ||
Ok, since my last post, I have slapped myself on the wrist. I made a newbie mistake. The function that I send the host, port, etc to was in the wrong order from an older version of the function I had. So... the port was "MSIE..." instead of "80". Way to go me! =\
Thanks Richard.
~Philip
On Nov 6, 2006, at 3:12 PM, Richard Lynch wrote:
Depending on your php.ini settings, it may be set up to wait FOREVER for a socket to open... What $host? What $port? Is it public? Private? Is there any authentication scheme in place? We've got nothing to work with here to help you... On Mon, November 6, 2006 2:58 pm, Philip Thompson wrote:Hi. I have not dealt much with fsockopen, but after looking at many examples, I'm not finding the answers I need. fsockopen is not returning anything and I'm trying to find out what the issue is. The error messages are not provided and I'm not sure what's going on. Help please! <? $fp = fsockopen($host, $port, $errno, $errstr); if (!$fp) {echo "fsock NOT opened!<br/>"; echo "Error: $errstr ($errno)<br />\n";} ?> Thanks, ~Philip