Apache-SAPI is effected by this patch too.
(patch is already committed)
Dmitry.
> -Original Message-
> From: Alex Kiesel [mailto:[EMAIL PROTECTED]
> Sent: Saturday, June 23, 2007 9:55 PM
> To: Dmitry Stogov
> Cc: 'internals Mailing List'
> Subject: R
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 aff
I thought the goal of the patch was to display an error page on things
like syntax errors?
Sure, one of.
in that case, set_error_code() would never be called..., even if it
Why not? PHP scripts often consist of dozens of files, and the fatal
error could happen in any of them beofre any outp
On 6/13/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Oh, sorry. The patch was filtered :)
> I am sendig it again.
>
> It is sapi independent.
I think we could extend it by allowing people to specify the error code
(and maybe also error string - though not sure it's needed) - something
lik
Oh, sorry. The patch was filtered :)
I am sendig it again.
It is sapi independent.
I think we could extend it by allowing people to specify the error code
(and maybe also error string - though not sure it's needed) - something
like set_error_code() function.
--
Stanislav Malyshev, Zend Produ
: 'internals Mailing List'; 'Stanislav Malyshev'; 'Andrei
> Nigmatulin'
> Subject: RE: [PHP-DEV] FW: php fastcgi
>
>
> Where is the propsed patch? I was thinking about a (not SAPI
> specific the subject indicates) modification to the
> php-out
On Wednesday 13 June 2007 22:17, Nicolas Bérard-Nault wrote:
> Hmm, maybe you're talking about 503, which is not exactly the same thing as
> 500.
>
> Take a look at RFC 2616, section 10.
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a
temporary o
Hmm, maybe you're talking about 503, which is not exactly the same thing as
500.
Take a look at RFC 2616, section 10.
On 6/13/07, Andrei Nigmatulin <[EMAIL PROTECTED]> wrote:
On Wednesday 13 June 2007 21:45, Nicolas Bérard-Nault wrote:
> Returning 404 (or any other code other than 500) does no
On Wednesday 13 June 2007 21:45, Nicolas Bérard-Nault wrote:
> Returning 404 (or any other code other than 500) does not make sense. If an
> user sees a Page not found error, he probably won't bother and won't come
> back / delete his bookmark. On the other hand, if a search engine bot
> stumbles u
Returning 404 (or any other code other than 500) does not make sense. If an
user sees a Page not found error, he probably won't bother and won't come
back / delete his bookmark. On the other hand, if a search engine bot
stumbles upon one of these, the page is automatically erased from the index,
n
On 6/13/07, Stanislav Malyshev <[EMAIL PROTECTED]> wrote:
> Configuaratin option make sense, but PHP already has too many configuration
> options especialliy for error reprting.
> I would like to avoid new ones.
set_error_code(500) (or set_error_code(404)) might help?
--
I am with set_error_co
x27;; 'Stanislav Malyshev'; 'Andrei Nigmatulin'
> Subject: RE: [PHP-DEV] FW: php fastcgi
>
> Configuaratin option make sense, but PHP already has too many
> configuration
> options especialliy for error reprting.
> I would like to avoid new ones.
>
> Th
Configuaratin option make sense, but PHP already has too many configuration
options especialliy for error reprting.
I would like to avoid new ones.
set_error_code(500) (or set_error_code(404)) might help?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/
--
P
; To: Dmitry Stogov
> Cc: 'internals Mailing List'; Stanislav Malyshev; Andrei Nigmatulin
> Subject: Re: [PHP-DEV] FW: php fastcgi
>
>
> On Wed, June 13, 2007 2:07 am, Dmitry Stogov wrote:
> > Current time most PHP instalations use setting
> 'display_error=0
On Wed, June 13, 2007 2:07 am, Dmitry Stogov wrote:
> 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
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?
On 13/06/07, Dmitry Stogov <[EMAIL PROTECTED]> wrote:
Hi,
Current time most PHP instalations use setting 'display_error=0'.
This setting hides errors
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
17 matches
Mail list logo
