From 394eafb840ae2fe0dd2ebde42d32b8b937e706ec Mon Sep 17 00:00:00 2001 From: Adrian Holovaty Date: Fri, 11 Nov 2005 00:25:03 +0000 Subject: [PATCH] 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 --- docs/middleware.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) 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