Avoid swallowing flask control-flow exceptions #158
The Flask 1.0 release changed the semantics of
Previously, this feature would catch application internal exceptions only. Since the Flask 1.0 release, this now catches all exceptions, including werkzeug's HTTPException which is used internally by Flask for control flow, e.g. 404 not found, 403 forbidden, etc. The side-effect of this change is that the AppInsights exception handler now translated these control flow exceptions into uncaught exceptions, i.e. HTTP 500 errors.
This change makes the AppInsights exception handler more robust to no longer swallow the control-flow exceptions.