diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2005-11-11 00:25:03 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2005-11-11 00:25:03 +0000 |
| commit | 394eafb840ae2fe0dd2ebde42d32b8b937e706ec (patch) | |
| tree | 1656d33a9e41a2b42f7d7e55e065aa3a3a3e7f3a | |
| parent | 8613b7436700520a37c8e4488ff4d7139af17899 (diff) | |
| download | django-394eafb840ae2fe0dd2ebde42d32b8b937e706ec.tar.gz | |
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
| -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 d920e88370..edaa5915e4 100644 --- a/docs/middleware.txt +++ b/docs/middleware.txt @@ -27,7 +27,8 @@ name. For example, here's the default ``MIDDLEWARE_CLASSES`` created by "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., ``MIDDLEWARE_CLASSES`` can be empty, if you'd like -- but it's strongly |