Opened 4 years ago

Closed 4 years ago

#12290 closed (wontfix)

Give an example for a default ordering of built-in Django middleware

Reported by: anonymous Owned by: nobody
Component: Documentation Version: 1.1
Severity: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


There are almost a dozen middleware classes built in in Django. However, figuring out in which order they should be embedded in the settings can get beyond a newbies reach in seconds.

Please update the documentation over at Built-in Middleware and add either:

  • a copy'n paste list for of how all middleware classes described there can be embedded


  • a more detailed "this must come before/after that" guideline

Attachments (0)

Change History (1)

comment:1 Changed 4 years ago by russellm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

There are only a couple of middlewares that are order dependent (e.g., GzipMiddleware, TransactionMiddleware), and their documentation describes that order dependence. Otherwise, the order is either unimportant, or entirely dependent on what you are trying to achieve.

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.