You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm creating a sub App instance with a custom error handler, then mount it to the main App instance. I found the custom error handler for the sub App instance is not effective.
I know this may not be a programming bug, but it seems like an unexpected behavior to me.
Also, i believe resolving this issue will help to address the following use case:
Imaging I have an HTTP service (main App instance) with two sub App instances, one for public API access and one for private API access. I'd like to custom different error handling for each instance, for example, outputting error logs to different targets.
Thanks for opening your first issue here! 馃帀 Be sure to follow the issue template! If you need help or want to chat with us, join us on Discord https://gofiber.io/discord
@AliasT Thanks for your advice, but i think middleware is incapable of catching and overriding error from the framework, for example, overriding the default plaintext 404 path not found error response to a json response.
Fiber version
v2.14.0
Issue description
I'm creating a sub App instance with a custom error handler, then mount it to the main App instance. I found the custom error handler for the sub App instance is not effective.
I know this may not be a programming bug, but it seems like an unexpected behavior to me.
Also, i believe resolving this issue will help to address the following use case:
Imaging I have an HTTP service (main App instance) with two sub App instances, one for public API access and one for private API access. I'd like to custom different error handling for each instance, for example, outputting error logs to different targets.
Code snippet
The text was updated successfully, but these errors were encountered: