maya-chen/flask
1
0
Fork 0
forked from orbit-oss/flask
Code Pull requests Activity

Invoke after_request on exceptions as well. This fixes #59

Browse source
This commit is contained in:
Armin Ronacher 2010-06-02 18:04:49 +02:00
parent ee69fb5890
commit 33e7f2b990
2 changed files with 45 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

13
flask.py
View file

@ -1362,6 +1362,12 @@ class Flask(_PackageBoundObject):
Then you still have the original application object around and
can continue to call methods on it.
.. versionchanged:: 0.4
The :meth:`after_request` functions are now called even if an
error handler took over request processing. This ensures that
even if an exception happens database have the chance to
properly close the connection.
:param environ: a WSGI environment
:param start_response: a callable accepting a status code,
a list of headers and an optional
@ -1376,6 +1382,13 @@ class Flask(_PackageBoundObject):
response = self.process_response(response)
except Exception, e:
response = self.make_response(self.handle_exception(e))
try:
response = self.process_response(response)
except Exception, e:
self.logger.exception('after_request handler failed '
'to postprocess error response. '
'Depending on uncertain state?')
return response(environ, start_response)
def request_context(self, environ):