RE: [PHP-DEV] error handling
| From: | John Coggeshall | Date: | Thu, 21 Nov 2002 12:10:11 +0000 |
| Subject: | RE: [PHP-DEV] error handling | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-91402@lists.php.net to get a copy of this message | ||
>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.
Check out my patch and tell me what you think. Since this can be turned
on/off (default will be off) we'll maintain the current "pretty" (sorta)
errors and it is completely platform-independant
>+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.
Again, check my patch out and let me know what you think.
John
>just my +.2c
>
>--
>Maxim Maletsky
>maxim@php.net
>
>
>
>"James Cox" <james@imajes.info> 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:john@coggeshall.org]
>> > 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:john@coggeshall.org]
>> > >> 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
>>
>
>