Re: [PHP-DEV] Re: One more critical problem in 5.4

2012-02-01 Thread Michael Wallner
On Wed, 01 Feb 2012 11:57:08 +0200, Lior Kaplan wrote: > On Tue, 2012-01-31 at 03:58 -0500, Michael Wallner wrote: >> On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: >> >> > Sorry, problem is not solved yet. >> >> I committed a possible fix to trunk. It's pretty much along the patch >

Re: [PHP-DEV] Re: One more critical problem in 5.4

2012-02-01 Thread jpauli
On Wed, Feb 1, 2012 at 10:57 AM, Lior Kaplan wrote: > On Tue, 2012-01-31 at 03:58 -0500, Michael Wallner wrote: > > On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: > > > > > Sorry, problem is not solved yet. > > > > I committed a possible fix to trunk. It's pretty much along > > the pa

Re: [PHP-DEV] Re: One more critical problem in 5.4

2012-02-01 Thread Lior Kaplan
On Tue, 2012-01-31 at 03:58 -0500, Michael Wallner wrote: > On Tue, 31 Jan 2012 10:04:34 +0200, yoram bar haim wrote: > > > Sorry, problem is not solved yet. > > I committed a possible fix to trunk. It's pretty much along > the patch from you, I just hat to fix crashes in the cli server > and ne

Re: [PHP-DEV] Re: One more critical problem in 5.4

2012-01-30 Thread Stas Malyshev
Hi! should be reproducible with this simple script: http://www.google.com";); Could you check with a recent checkout? Looks like the last patch from Michael fixed that (at least it works for me). -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext

Re: [PHP-DEV] Re: One more critical problem in 5.4

2012-01-30 Thread yoram bar haim
As I sayed, my patch was not suggusted as fix, Dmitry is write about possible side effetcs, it was added only to prove that the problem is what we think it is. On Monday, January 30, 2012 05:42:11 PM Dmitry Stogov wrote: > Hi Mike, > > I confirm the bug. In case of empty output HTTP headers are

Re: [PHP-DEV] Re: One more critical problem in 5.4

2012-01-30 Thread Dmitry Stogov
Hi Mike, I confirm the bug. In case of empty output HTTP headers are sent to stdout or stderr instead of FastCGI stream. To reproduce I configured nginx to use PHP FastCGI server on UNIX socket, then launched (sapi/cgi/php-cgi -b /tmp/fcgi-php5) and performed several request to empty PHP fil