Hi,
Current time most PHP instalations use setting 'display_error=0'.
This setting hides errors from user but may send to him just a blank page.
The proposed patch sends HTTP 500 response on errors instead of blank pages.
The pages that already wrote something are not affectd.
Any objections or additions?
Thanks. Dmitry.
I think that's a good idea.
But wouldn't letting this be controlled in userland via
set_error_handler / set_exception_handler be just as good?
Hi,
Current time most PHP instalations use setting 'display_error=0'.
This setting hides errors from user but may send to him just a blank page.The proposed patch sends HTTP 500 response on errors instead of blank pages.
The pages that already wrote something are not affectd.Any objections or additions?
Thanks. Dmitry.
--
--
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"
Current time most PHP instalations use setting 'display_error=0'.
This setting hides errors from user but may send to him just a blank
page.The proposed patch sends HTTP 500 response on errors instead of blank
pages.
The pages that already wrote something are not affectd.Any objections or additions?
This sounds perfectly reasonable...
But I suspect some users might prefer a 404 or a customizable response
of some type...
At the risk of incurring the wrath of list members, perhaps yet
another php.ini configuration switch could be considered?...
I wouldn't hold up the 500 patch for long with this kind of
discussion, but it's worth taking a few minutes to consider, I think.
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some indie artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?
Dmitry Stogov schrieb:
Hi,
Current time most PHP instalations use setting 'display_error=0'.
This setting hides errors from user but may send to him just a blank page.The proposed patch sends HTTP 500 response on errors instead of blank pages.
The pages that already wrote something are not affectd.Any objections or additions?
Is there any change to change Apache(2)-Sapi dependent code, so that the
HTTP status is propagated to the Apache process and an ErrorDocument
will be triggered [1]?
Otherwise, the user still ends up with a blank page...
[1] http://www.thescripts.com/forum/thread644678.html
Regards,
-Alex