Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:57830
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F393F54.4040109@srce.hr>
References: <4F393F54.4040109@srce.hr>
Date: Mon, 13 Feb 2012 17:55:19 +0100
Message-ID: <CAH-PCH4XKwmFJOnBr69cAfS7Xg3gqhSBuqq_yJqhBSbZV3NDoQ@mail.gmail.com>
To: Jakov Sosic <jakov.sosic@srce.hr>
Cc: PHP Developers Mailing List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=002354471334f800ab04b8db5762
Subject: Re: [PHP-DEV] Internal server error on PHP syntax error?
From: tyra3l@gmail.com (Ferenc Kovacs)

--002354471334f800ab04b8db5762
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Feb 13, 2012 at 5:50 PM, Jakov Sosic <jakov.sosic@srce.hr> wrote:

> Hi.
>
> I don't know if this is the right group to ask this kind of question, but
> if it isn't please excuse my french ;)
>
> As far as I can see, PHP does not report back to Apache error 500 in case
> of a syntax error in code but displays empty page. For example this code:
>
> <?php foobar();
>
> always returns empty page.
>
> I was curious, so I googled little around and found this old entry from
> this mailing list:
>
> http://marc.info/?l=3Dphp-**internals&m=3D124043575308005<http://marc.inf=
o/?l=3Dphp-internals&m=3D124043575308005>
>
>
> So if that's true, and if I understand it correctly, there is no way for
> Apache to display error 500 in case of PHP syntax error?
>
>
It is implemented already, php will report HTTP 500 on fatal errors, except
if the headers were already sent.
And I also remember a php/xdebug bug, which caused the headers to be sent
see http://bugs.xdebug.org/view.php?id=3D587 and
https://bugs.php.net/bug.php?id=3D50921
Derick fixed it in 5.4
So I would suggest you to double-check that you aren't using xdebug when
you experience the problem, and that you don't send out the headers before
your code blows up.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--002354471334f800ab04b8db5762--