Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53558 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 34141 invoked from network); 23 Jun 2011 21:37:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jun 2011 21:37:37 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass; domainkeys=bad Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.170 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.160.170 mail-gy0-f170.google.com Received: from [209.85.160.170] ([209.85.160.170:46176] helo=mail-gy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 76/B8-19628-022B30E4 for ; Thu, 23 Jun 2011 17:37:36 -0400 Received: by gye5 with SMTP id 5so1060916gye.29 for ; Thu, 23 Jun 2011 14:37:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=GSSsoGIKHx0PlKjAX0s8DQYdniETNxknH3y69dgmrH4=; b=PjmcFWE70CGtI9eDlA/UjI+V8/OZutSZm5OHXUYQVJ8dKpvV+/DYz7GQfLXOBkuiwu cwojMtI5Xg7EoN5qI90EhiQ7SJr4S8L+MmOHegl8LARtNkTfLVrGWsq3leqU4BiL+k+W RbcaxxRFK8HO3JX09HWTF1sX+9iYOc+2HcCaA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cwPD7WE91VgSIu/3n2e5vUP19FB6S+m0D9UvWiPsbH8b5kJ2nE3hWpzgtn1LWpcZ5T EXvmc5JgW7ggMtBWZhX8ToyMs1V/6AgiHfDnF4BRIUNHCPNvgONYYxbwU9qm6ezL9ZUF +j+IZ1GWUsfTCMArjuBMNI/T3NuFJwNTBWecs= MIME-Version: 1.0 Received: by 10.147.100.20 with SMTP id c20mr2766222yam.5.1308865053328; Thu, 23 Jun 2011 14:37:33 -0700 (PDT) Received: by 10.147.99.3 with HTTP; Thu, 23 Jun 2011 14:37:33 -0700 (PDT) In-Reply-To: <4E03AFFA.7060005@sugarcrm.com> References: <4E03AFFA.7060005@sugarcrm.com> Date: Thu, 23 Jun 2011 23:37:33 +0200 Message-ID: To: Stas Malyshev Cc: Derick Rethans , PHP Developers Mailing List Content-Type: multipart/alternative; boundary=000e0cd3a9b890068c04a667e493 Subject: Re: [PHP-DEV] html_errors default settings From: tyra3l@gmail.com (Ferenc Kovacs) --000e0cd3a9b890068c04a667e493 Content-Type: text/plain; charset=UTF-8 On Thu, Jun 23, 2011 at 11:28 PM, Stas Malyshev wrote: > Hi! > > > On 6/23/11 12:47 PM, Derick Rethans wrote: > >> I'd like to revert this change *and* change when the docrefs are >> shown, so that in 5.4 and trunk: >> - html_errors is on by default again. >> - the docref links are only shown when docref_root is not empty >> >> A patch is attached. Comments? >> > > Thinking more about this: if we're in production, that means display_errors > is off. So where exactly we expect to have these HTML errors and how they > are useful? > > I have no idea why specific settings of xdebug depend on html_errors and > why xdebug can't have its own configuration setting to fix it if needed - > but this has nothing to do with PHP defaults IMO. I'd like to hear and > explanation how production setting of html_errors as 1 is useful. > > xdebug does some fancy html around the output of the stack trace/var_dump calls, and it only does that if html_errors is enabled. usually you don't use xdebug in production, so it really doesn't matter much. but because we suggest in the production ini that it has a performance and security impact, distros ships with html_errors turned off, which prevents xdebug from enhancing the output. I think that this could be changed back how it was before, but if many of you think that this is a bad idea, then probably Derick should stop using this config option for controlling this particular feature in xdebug, and he could introduce a new option. Tyrael --000e0cd3a9b890068c04a667e493--