mirror of
https://github.com/django/django.git
synced 2025-11-02 04:48:33 +00:00
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.
This commit is contained in:
parent
beec05686c
commit
756c390fb5
2 changed files with 71 additions and 1 deletions
|
|
@ -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
|
||||
===========================
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue