Code

Opened 7 years ago

Closed 7 years ago

#4324 closed (wontfix)

Middleware order matters.

Reported by: cdome@… Owned by: jacob
Component: Documentation Version: master
Severity: Keywords: Middleware order
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

It is clearly stated that the order, in which middlewares are added, is important, but nowhere to find in the doc what is the correct order. I have to go though all documentation in order to asure myself that I haven't broken anything.
I think page http://www.djangoproject.com/documentation/middleware/ lacks an example with MIDDLEWARE_CLASSES set to the list of middlewares, but ALL middlewares are specified in appropriate order, including django.contribs. Then, any one can get what the order should be, by looking at it.

Attachments (0)

Change History (1)

comment:1 Changed 7 years ago by jacob

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

Though the order is worth thinking about, there isn't one "standard" order. The documentation for each middleware explains how early it needs to be, and from there it doesn't really matter. We don't want to make it appear that there's only a single order allowed; that would obfuscate the meaning of the ordering.

Add Comment

Modify Ticket

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


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

 
Note: See TracTickets for help on using tickets.