Re: parse errors no longer visible

From: Date: Thu, 24 Apr 2003 17:08:21 +0000
Subject: Re: parse errors no longer visible
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-1030@lists.php.net to get a copy of this message
Hi Derick, ----- Original Message ----- From: "Derick Rethans" <derick@php.net> To: "Zeev Suraski" <zeev@zend.com> Cc: "PHP Developers Mailing List" <internals@lists.php.net> Sent: Thursday, April 24, 2003 4:03 AM Subject: Re: [PHP-DEV] parse errors no longer visible > On Wed, 23 Apr 2003, Zeev Suraski wrote: > > > I have no problem getting a parse error to be shown, can you describe what > > you did to get that behavior? > > Oh, that's easy: [snip] > 2. Use no php.ini: > > and request the page... you'll see no error. In your first email you mention that you had modified the error_reporting value in php.ini. In this email you said that no php.ini was used. However, there is one more value that you'll want to check: ; - display_errors = Off [Security] ; With this directive set to off, errors that occur during the execution of ; scripts will no longer be displayed as a part of the script output, and thus, ; will no longer be exposed to remote users. With some errors, the error message ; content may expose information about your script, web server, or database ; server that may be exploitable for hacking. Production sites should have this ; directive set to off. > > Derick Hope that helps! - Marshall

« previous php.internals (#1030) next »