Re: HTTP_Client or Net_Socket bug?
| From: | Chuck Hagenbuch | Date: | Tue, 16 Nov 2004 15:14:52 +0000 |
| Subject: | Re: HTTP_Client or Net_Socket bug? | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-34412@lists.php.net to get a copy of this message | ||
Quoting Andrew Nagy <asnagy@webitecture.org>:
Yup, according to netcraft it is a Win2k with IIS 5. I am using the latest version of Net_Socket, unless the code in CVS has been updated?Right. This commit fixed the problem: http://cvs.php.net/diff.php/pear/Net_Socket/Socket.php?r1=1.16&r2=1.17&ty=h The latest release is 1.0.2, though, many months ago. The reason is that I haven't made a new release since this: http://cvs.php.net/diff.php/pear/Net_Socket/Socket.php?r1=1.9&r2=1.10&ty=h It fixes many problems for folks, but technically by current PEAR BC rules it can't be released, at least under the same name. But releasing it as Net_Socket2 is a nightmare and a half for all the packages that use Net_Socket. So we're at a stalemate. Do I remember correctly that progress has been made on the impact of extending PEAR? Or only on including it?
It must be an issue with IIS5 because I am connecting to other sites that use SSL and do not cause the warning.Correct. -chuck -- "But she goes not abroad in search of monsters to destroy." - John Quincy Adams