Updated docs/middleware.txt to say exception middleware is applied in reverse order.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@1162 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
394eafb840
commit
d38e882695
|
@ -28,7 +28,8 @@ name. For example, here's the default ``MIDDLEWARE_CLASSES`` created by
|
||||||
)
|
)
|
||||||
|
|
||||||
Django applies middleware in the order it's defined in ``MIDDLEWARE_CLASSES``,
|
Django applies middleware in the order it's defined in ``MIDDLEWARE_CLASSES``,
|
||||||
except in the case of response middleware, which is applied in reverse order.
|
except in the case of response and exception middleware, which is applied in
|
||||||
|
reverse order.
|
||||||
|
|
||||||
A Django installation doesn't require any middleware -- e.g.,
|
A Django installation doesn't require any middleware -- e.g.,
|
||||||
``MIDDLEWARE_CLASSES`` can be empty, if you'd like -- but it's strongly
|
``MIDDLEWARE_CLASSES`` can be empty, if you'd like -- but it's strongly
|
||||||
|
|
Loading…
Reference in New Issue