summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorJames Bennett <ubernostrum@gmail.com>2010-03-03 08:52:51 +0000
committerJames Bennett <ubernostrum@gmail.com>2010-03-03 08:52:51 +0000
commit36e7739d9d08cd83c9cc6be56ea33443ac26b484 (patch)
tree4d14a40fb5b45684296a819144600eda45ad5296 /docs/ref
parent7adae3028656cb8ea6c2c2c30a7bc747f7e26796 (diff)
[1.1.X] Fixed #12217: Documented the fact that serving flatpages from the flatpage middleware does not apply view middleware methods. Backport of [12671] from trunk.
git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12672 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/contrib/flatpages.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/ref/contrib/flatpages.txt b/docs/ref/contrib/flatpages.txt
index 7c65e0a30b..bca1c7a9c1 100644
--- a/docs/ref/contrib/flatpages.txt
+++ b/docs/ref/contrib/flatpages.txt
@@ -80,6 +80,14 @@ If it doesn't find a match, the request continues to be processed as usual.
The middleware only gets activated for 404s -- not for 500s or responses of any
other status code.
+.. admonition:: Flatpages will not apply view middleware
+
+ Because the ``FlatpageFallbackMiddleware`` is applied only after
+ URL resolution has failed and produced a 404, the response it
+ returns will not apply any :ref:`view middleware <view-middlware>`
+ methods. Only requests which are successfully routed to a view via
+ normal URL resolution apply view middleware.
+
Note that the order of :setting:`MIDDLEWARE_CLASSES` matters. Generally, you can
put :class:`~django.contrib.flatpages.middleware.FlatpageFallbackMiddleware` at
the end of the list, because it's a last resort.