Project

General

Profile

Improvements #10137

Uncaught exceptions in handleRequest crash the application

Added by Roel Standaert 8 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Target version:
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.

#1

Updated by Roel Standaert 8 months ago

  • Description updated (diff)
#2

Updated by Roel Standaert 5 months ago

  • Status changed from New to InProgress
  • Assignee set to Roel Standaert
#3

Updated by Roel Standaert 5 months ago

  • Status changed from InProgress to Review
  • Assignee deleted (Roel Standaert)
#4

Updated by Roel Standaert 5 months ago

  • Status changed from Review to Implemented @Emweb
#5

Updated by Roel Standaert 5 months ago

  • % Done changed from 0 to 100
#6

Updated by Roel Standaert 5 months ago

  • Status changed from Implemented @Emweb to Resolved
#7

Updated by Roel Standaert 5 months ago

  • Assignee set to Roel Standaert
#8

Updated by Roel Standaert 5 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF