Doc #62891 [Opn->Wfx]: Error codes
| From: | aharvey@php.net | Date: | Thu, 23 Aug 2012 01:15:15 +0000 |
| Subject: | Doc #62891 [Opn->Wfx]: Error codes | ||
| References: | 1 | Groups: | php.doc.bugs |
| Request: | Send a blank email to doc-bugs+get-8752@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=62891&edit=1
ID: 62891
Updated by: aharvey@php.net
Reported by: dagguh at gmail dot com
Summary: Error codes
-Status: Open
+Status: Wont fix
Type: Documentation Problem
-Package: Sockets related
+Package: Documentation problem
PHP Version: Irrelevant
Block user comment: N
Private report: N
New Comment:
Ultimately, the error codes in I/O-related warning and error messages are entirely OS-dependent. I
don't think there's a lot we can do here that would make things better rather than worse:
trying to cover the common cases may only lead to confusion for people using less common operating
systems.
Previous Comments:
------------------------------------------------------------------------
[2012-08-22 12:09:15] dagguh at gmail dot com
Description:
------------
---
From manual page: http://www.php.net/function.fsockopen
---
Error codes are not documented. Error messages might be insufficient or simply
wrong.
We are getting error code 146 with error message "Connection refused".
Our network team state that there is no possibility of connection being refused,
because the machines are in the same subnetwork.
We are using fsockopen with a 1 second timeout. I wonder if this error is simply
the timeout, but fsockopen reports wrong error.
If error codes were documented, we would be sure what exactly "Connection
refused" means and maybe we would see a seperate error for a timeout.
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=62891&edit=1