500 errors rendered in Production

[francisdb]

I tried a GET for a route that does not exist and got this:

Running On IHP Cloud

default config option Production

I would expect that such info would be logged but not returned to the end user as it might contain sensitive information Also should this not just return 404?

rev = "943431d4dfeda5236961073e5895670b0fce2da6"

[mpscholten]

Hey, the error handling behavior has changed in v0.8 to render a generic error page for all exceptions thrown during the execution of an action.

The routing logic has it's own error handler. I think there's a few cases where we don't correctly display the generic error page during routing yet. So this is likely a bug.

[MonaMayrhofer]

What's the state on this currently?

I'm getting (among others) the "Database looks outdated" error because of missing migrations in Production mode - including that really shouldn't be client facing. Is this expected or am I just doing something wrong?

[mpscholten]

Could you verify that you are running with IHP_ENV=Production? The migration error should only be shown in dev mode

[MonaMayrhofer]

Yes, oops, my fault i hadn't noticed i wasn't.