Updated middleware.txt to note that response middleware is applied in reverse

git-svn-id: http://code.djangoproject.com/svn/django/trunk@1161 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2005-11-11 00:25:03 +00:00
parent 8613b74367
commit 394eafb840
1 changed files with 2 additions and 1 deletions

View File

@ -27,7 +27,8 @@ name. For example, here's the default ``MIDDLEWARE_CLASSES`` created by
"django.middleware.doc.XViewMiddleware", "django.middleware.doc.XViewMiddleware",
) )
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.
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