[EMAIL PROTECTED] wrote:
> What Perrin already stated is very true. You don't want the world to see
> these things.
> 
> I made a few lines in my httpd.conf saying:
> 
>         ErrorDocument 500 /error/fatal/
>         ErrorDocument 403 /error/access/
>         ErrorDocument 404 /error/notfound/
> 
> ...for the VirtualHost running this Mason site.
> 
> Inside these dirs I then output a nicely formatted error message that is
> readable, and understandable to the user. And best of all - it's inside my
> layout/structure of my site - looking very pro and stylish - even though
> it's a fatal error ;)
> 
> I still get the errorstack in my apache log, so it's not blinding me
> completely :)
> 
> I'm still dwelling on weather I want the system to log errors to a database,
> or a custom logfile - so I get all the info I want (user IP, session data
> and so forth).
> 
> But also have a look in the docs under:
> 
> http://masonhq.com/docs/manual/Admin.html#error_reporting_and_exceptions
> 
> That should give you a head start on handling errors more elegantly :)
> 
>  - Nicolai
> 
> 
Thanks for the tip Nicolai...

:Robert



_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users

Reply via email to