Bug #54896 [Com]: Connection to localhost doesn't work in Apache SAPI but works in CLI and CGI

From: Date: Thu, 02 Jun 2011 17:57:53 +0000
Subject: Bug #54896 [Com]: Connection to localhost doesn't work in Apache SAPI but works in CLI and CGI
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-161135@lists.php.net to get a copy of this message
Edit report at http://bugs.php.net/bug.php?id=54896&edit=1

 ID:                 54896
 Comment by:         neweracracker at gmail dot com
 Reported by:        neweracracker at gmail dot com
 Summary:            Connection to localhost doesn't work in Apache SAPI
                     but works in CLI and CGI
 Status:             Closed
 Type:               Bug
 Package:            Streams related
 Operating System:   Windows 7
 PHP Version:        5.3SVN-2011-05-20 (snap)
 Assigned To:        cataphract
 Block user comment: N
 Private report:     N

 New Comment:

It works :D


Previous Comments:
------------------------------------------------------------------------
[2011-06-02 18:30:39] cataphract@php.net

I'm confident this can be closed now.

------------------------------------------------------------------------
[2011-06-02 10:54:43] cataphract@php.net

Please test the snapshot for revision 311730, when available.

------------------------------------------------------------------------
[2011-06-02 10:46:42] cataphract@php.net

Automatic comment from SVN on behalf of cataphract
Revision: http://svn.php.net/viewvc/?view=revision&revision=311730
Log: - Fixed double registering of browscap ini directive. See bug #54896.

------------------------------------------------------------------------
[2011-06-01 19:59:07] cataphract@php.net

Possibly the merge to 5.3 has butchered something.

This is caused by the timeout being too low because the ini entry default_socket_timeout is not
registered (doesn't appear in phpinfo()). If you pass fsockopen a timeout of, say, 10s, it
works correctly. 

I'll take a closer look later today.

------------------------------------------------------------------------
[2011-06-01 19:43:40] neweracracker at gmail dot com

Exactly :)

Please review your browser fix since it seems to have caused this.

Thank you.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    http://bugs.php.net/bug.php?id=54896


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=54896&edit=1


Thread (17 messages)

« previous php.bugs (#161135) next »