Actions
Improvements #10137
closedUncaught exceptions in handleRequest crash the application
Start date:
04/08/2022
Due date:
% Done:
100%
Estimated time:
Description
In the past I wasn't quite so sure about whether or not we should catch all exceptions in WResource::handleRequest
by default.
Arguments for catching exceptions:
- programming errors don't crash the entire application, which is probably preferred in production
Arguments for not catching:
- not catching makes developers using Wt notice the error, and allow them to debug and fix them. Catching and logging is less obvious than crashing.
I think we should catch by default, and perhaps allow developers to turn it off to facilitate debugging.
Updated by Roel Standaert over 2 years ago
- Status changed from New to InProgress
- Assignee set to Roel Standaert
Updated by Roel Standaert over 2 years ago
- Status changed from InProgress to Review
- Assignee deleted (
Roel Standaert)
Updated by Roel Standaert over 2 years ago
- Status changed from Review to Implemented @Emweb
Updated by Roel Standaert over 2 years ago
- Status changed from Implemented @Emweb to Resolved
Updated by Roel Standaert over 2 years ago
- Status changed from Resolved to Closed
Actions