diff options
author | Adrian Holovaty <adrian@holovaty.com> | 2005-11-11 01:14:02 +0000 |
---|---|---|
committer | Adrian Holovaty <adrian@holovaty.com> | 2005-11-11 01:14:02 +0000 |
commit | d38e882695f7cbeed645346281eaa9b651619a48 (patch) | |
tree | 92647658970066074b3682f2a0b4236f4c82fd19 | |
parent | 394eafb840ae2fe0dd2ebde42d32b8b937e706ec (diff) | |
download | django-d38e882695f7cbeed645346281eaa9b651619a48.tar.gz |
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
-rw-r--r-- | docs/middleware.txt | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/middleware.txt b/docs/middleware.txt index edaa5915e4..a7a5474d84 100644 --- a/docs/middleware.txt +++ b/docs/middleware.txt @@ -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``, -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., ``MIDDLEWARE_CLASSES`` can be empty, if you'd like -- but it's strongly |