Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:57836 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79819 invoked from network); 13 Feb 2012 21:12:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Feb 2012 21:12:03 -0000 Authentication-Results: pb1.pair.com header.from=jakov.sosic@srce.hr; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=jakov.sosic@srce.hr; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain srce.hr designates 161.53.2.69 as permitted sender) X-PHP-List-Original-Sender: jakov.sosic@srce.hr X-Host-Fingerprint: 161.53.2.69 regoc.srce.hr Linux 2.6 Received: from [161.53.2.69] ([161.53.2.69:41571] helo=smtp.srce.hr) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 13/B3-61403-D9C793F4 for ; Mon, 13 Feb 2012 16:11:58 -0500 Received: from localhost (localhost [127.0.0.1]) by smtp.srce.hr (Postfix) with ESMTP id 0119115D605 for ; Mon, 13 Feb 2012 22:11:54 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at regoc.srce.hr Received: from smtp.srce.hr ([127.0.0.1]) by localhost (regoc.srce.hr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X61zqjpMw2i0 for ; Mon, 13 Feb 2012 22:11:51 +0100 (CET) Received: from nb-jsosic.srce.hr (unknown [95.168.99.81]) by smtp.srce.hr (Postfix) with ESMTPSA id 6159715D60F for ; Mon, 13 Feb 2012 22:11:51 +0100 (CET) Message-ID: <4F397C96.2040901@srce.hr> Date: Mon, 13 Feb 2012 22:11:50 +0100 Organization: Srce User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1 MIME-Version: 1.0 CC: internals@lists.php.net References: <4F393F54.4040109@srce.hr> <4F394381.7060103@srce.hr> <4F39441F.4000301@thelounge.net> In-Reply-To: <4F39441F.4000301@thelounge.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Internal server error on PHP syntax error? From: jakov.sosic@srce.hr (Jakov Sosic) On 02/13/2012 06:10 PM, Reindl Harald wrote: > yes, but the more important is the status code so that search > engines do not index you broken page, apache SHOULD NOT provide > his own error-page because you can also send 500 status code > within your script for whatever reason and want your output > not supressed in such cases OK but I would like it provide it's own error page... Is it possible somehow without patching php code and maintaining/compiling my own version? -- Jakov Sosic www.srce.unizg.hr