The point is that it should be possible to throw a HTTP 500 error. This is really only useful in production environments, ie, when the code going live should already be free of things like parse errors. Throwing a 500 error would make it easier to merge into your already existing error handling systems -- eg, for 404.
-- james > -----Original Message----- > From: Maxim Maletsky [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 21, 2002 12:15 PM > To: James Cox > Cc: [EMAIL PROTECTED]; 'PHP Developers Mailing List' > Subject: Re: [PHP-DEV] error handling > > > > Writing for newbies, I often heard them mentioning one things > they liked about > PHP (before even trying to use it) - "PHP errors are not 500 weird pages > made by your browser". > > Moving fatal errors to HTTP 500 can be somewhat confusing, unless we > have a solid way handling ALL errors in some very logical way. In other > words - powerful but clear enough to understand and use for neo > programmers. > > +1 to what someone mentioned earlier - PHP is not *only* for web, it is > *primarily* for web. Maybe, using HTTP headers for error handling would > make this less obvious. > > just my +.2c > > -- > Maxim Maletsky > [EMAIL PROTECTED] > > > > "James Cox" <[EMAIL PROTECTED]> wrote... : > > > it can; 500 means server error -- perl, cgi, mod_include, etc > all do it, so > > why shouldn't php? > > > > -- james > > > > > -----Original Message----- > > > From: John Coggeshall [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, November 20, 2002 11:06 PM > > > To: 'James Cox' > > > Cc: 'PHP Developers Mailing List' > > > Subject: RE: [PHP-DEV] error handling > > > > > > > > > > > > >true... > > > > > > > >i'd like to see a 500 error though, and some persistent vars... > > > > > > See, the problem that I'm seeing here is that I don't believe PHP is > > > reponsible for setting the error code returned by PHP.. For > instance, a > > > 404 error isn't handle by PHP at all. Likewise, I don't think PHP can > > > say "turn this into a 500 error" to Apache. > > > > > > John > > > > > > > > > > > > > > -- james > > > > > > > >> -----Original Message----- > > > >> From: John Coggeshall [mailto:[EMAIL PROTECTED]] > > > >> Sent: Wednesday, November 20, 2002 10:48 PM > > > >> To: 'James Cox' > > > >> Subject: RE: [PHP-DEV] error handling > > > >> > > > >> > > > >> >that can't really be done because parsing has happened, and so > > > >> >output has started -- but if we return status 500, the > > > >> >webserver can manage it properly.. > > > >> > > > >> Only if output buffering is off. Custom error handling should have > > > >> output buffering on anyway as I've already said... John > > > >> > > > >> > > > > > > > > > > > > > > > > -- > > PHP Development Mailing List <http://www.php.net/> > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
