forked from orbit-oss/flask
fix RST line too long
This commit is contained in:
parent
c5c8bbc7f6
commit
6606a4a238
15 changed files with 104 additions and 89 deletions
|
|
@ -258,13 +258,14 @@ Here is an example for a "404 Page Not Found" exception::
|
|||
|
||||
Most errorhandlers will simply work as expected; however, there is a caveat
|
||||
concerning handlers for 404 and 405 exceptions. These errorhandlers are only
|
||||
invoked from an appropriate ``raise`` statement or a call to ``abort`` in another
|
||||
of the blueprint's view functions; they are not invoked by, e.g., an invalid URL
|
||||
access. This is because the blueprint does not "own" a certain URL space, so
|
||||
the application instance has no way of knowing which blueprint errorhandler it
|
||||
should run if given an invalid URL. If you would like to execute different
|
||||
handling strategies for these errors based on URL prefixes, they may be defined
|
||||
at the application level using the ``request`` proxy object::
|
||||
invoked from an appropriate ``raise`` statement or a call to ``abort``
|
||||
in another of the blueprint's view functions; they are not invoked by,
|
||||
e.g., an invalid URL access. This is because the blueprint does not
|
||||
"own" a certain URL space, so the application instance has no way of
|
||||
knowing which blueprint errorhandler it should run if given an invalid URL.
|
||||
If you would like to execute different handling strategies for these errors
|
||||
based on URL prefixes, they may be defined at the application level using
|
||||
the ``request`` proxy object::
|
||||
|
||||
@app.errorhandler(404)
|
||||
@app.errorhandler(405)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue