Custom exception handlers about flask-cors HOT 2 CLOSED

Hey Daniel,

When used as a decorator, flask-Cors should not intercept exceptions or
alter them in any way. In order to get the expected behavior of adding Cors
headers to your error messages, decorate your error handler.

I will investigate more tonight to make sure it is doing what I expect! And
see if there is anyway to make it better. In the mean time, I encourage you
to use the extension, which should be simpler, and correctly wrap
exceptions.

Cheers,
Cory
On Sun, Apr 5, 2015 at 5:41 PM Cory Dolphin [email protected] wrote:

Hey
On Sun, Apr 5, 2015 at 11:08 AM Daniel Manson [email protected]
wrote:

Suppose I have:

@app.route('/doit')@cross_origin(origins='')def doit():
raise CustomException("owch!")
@app.errorhandler(CustomException)def handle_custom(err):
return str(err)

Surely the expected output should be the error page with cors headers?
But this is not what I find: I get an empty response with the 4xx error
code and nothing else (and no stacktrace on the server).

If this is intended behavior it should be made much clearer somewhere in
the docs as it confused me for a long time (though admittedly I am
completely new to flask cors and http error handling). Ideally though, the
expected behavior should be implemented, i.e. the error handler should
check the route function to see what cors it had intended to supply and
then provide them on the error response.

—
Reply to this email directly or view it on GitHub
#120.

from flask-cors.

@corydolphin any plans to add CORS to exceptions?

I am debugging a tricky exception on Chrome, without CORS, I can not see the tracebacks.

from flask-cors.