Re: [gentoo-server] handling syntax/parse errors with PHP

[Brian Kroth]

Definitely look at the php.ini.  Also, you might want to have a look at this:

http://www.modsecurity.org/

It has output filtering and a nice set of "Core Rules" that I think might even
have an option for things like this.  There's quite a lot of neat tricks you
can do with it.

Brian

Jil Larner <jil@××××.eu>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> In theory, a production server shouldn't have files with parse errors.
> It may be why there's no easy way to handle such an error. So I cannot
> give you the way to show a custom error page.
> But, for the second point, you may use php.ini' setting like log_errors,
> error_log (the logfile path), and ignore_repeated_errors in order to
> keep a little file. So you can parse this file and then send a mail, or
> whatever you want to do with errors.
>
> I hope it can help you. If you find a way to redirect on such error,
> i'll be happy to know how to do ;)
>
> Jil Larner.
>
> Andrew Gaffney a écrit :
> > In my PHP-based websites for work, I have some error handling code that
> > captures any errors, displays a "friendly" error page, and then sends me
> > an email with all the details about the error.
> >
> > However, this doesn't work for syntax/parse errors in pages, since the
> > code is not actually executed in this case. I can't seem to find
> > anything online about capturing these errors and notifying myself somehow.
> >
> > Does anyone do something like this already?
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
>
> iD8DBQFHTG0gMBDlpRaep+4RAjlaAKDa872UZIwZ7SLglKduspga3P7rYACg1jk+
> NHCZWsPT5Y2UAJJgk+Gm8Yk=
> =qkrR
> -----END PGP SIGNATURE-----
> --
> gentoo-server@g.o mailing list
>