diff options
| author | Claude Paroz <claude@2xlibre.net> | 2014-05-22 17:08:32 +0200 |
|---|---|---|
| committer | Claude Paroz <claude@2xlibre.net> | 2014-05-22 18:34:00 +0200 |
| commit | 1f6b3cf145fc1057f478607c2c845e66efaaf546 (patch) | |
| tree | 98216fb993514fcf8c67e660e92b716eee14ebe8 /docs/topics | |
| parent | 7d4a51e239bcde34d1614877accb3aa5f5589e0c (diff) | |
[1.7.x] Fixed #20816 -- Added hints about Django middleware ordering
Thanks gthb Trac user for the report, kolypto StackOverflow
user for the initial list and Tim Graham for the review.
Backport of 756c390fb5 from master.
Diffstat (limited to 'docs/topics')
| -rw-r--r-- | docs/topics/http/middleware.txt | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/topics/http/middleware.txt b/docs/topics/http/middleware.txt index b18573f002..a2b71dc664 100644 --- a/docs/topics/http/middleware.txt +++ b/docs/topics/http/middleware.txt @@ -45,7 +45,9 @@ The order in :setting:`MIDDLEWARE_CLASSES` matters because a middleware can depend on other middleware. For instance, :class:`~django.contrib.auth.middleware.AuthenticationMiddleware` stores the authenticated user in the session; therefore, it must run after -:class:`~django.contrib.sessions.middleware.SessionMiddleware`. +:class:`~django.contrib.sessions.middleware.SessionMiddleware`. See +:ref:`middleware-ordering` for some common hints about ordering of Django +middleware classes. Hooks and application order =========================== |