Opened 15 years ago
Closed 15 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: | no | UI/UX: | no |
Description
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 settings.py of how all middleware classes described there can be embedded
or
- a more detailed "this must come before/after that" guideline
Note:
See TracTickets
for help on using tickets.
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.