Error 500 page exposes site details to visitors

[gitname]

Even with the Display errors option set to No...

..., the Error 500 page (example shown below) still exposes more information than I would like it to while in Production.

Specifically, it does 2 things I want to change:

1. It has the known appearance of a Grav Error 500 page (providing a clue to the visitor that the site uses Grav and is vulnerable to any outstanding vulnerabilities in Grav)
2. It shows the PHP error information (providing a clue to the visitor of potential vulnerabilities in the site)

I would like to be able to customize the page, to disable it completely, or for there to be a Grav option I can use to indicate whether I want it to contain the PHP error information or not.

[Perlkonig]

I concur. When "display errors" is set to false, it should return a bare 500 and let the web server handle it. I'm looking through the source code but don't understand Whoops enough to know what the alternatives are. What would happen if you just returned Handler::Quit in this function? Why does Grav want to handle it in the first place? I'll do a little digging.

[Perlkonig]

A bare Handler::Quit seems to work. Something to consider, anyway.

[rhukster]

Done.