#24796: Middleware ordering hints don't mention SecurityMiddleware
--------------------------------------+------------------------------------
Reporter: TaymonB | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by carljm):
Tim, do you recall why you put it at the bottom of the list when you did
the integration?
I think I recommended top of the list in the django-secure docs just
because I figured if you're going to turn on the redirect-to-HTTPS, it may
as well happen sooner rather than after running through a bunch of other
unnecessary middleware.
Trying to think what the reasoning would be for having it at the bottom of
the list: I guess if you had other middleware that wanted to access the
value of some headers set by SecurityMiddleware?
Mostly I think it just really doesn't matter very much where you put it,
unless you're in an unusual situation.
--
Ticket URL: <https://code.djangoproject.com/ticket/24796#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.193d617fa4f8d36f3ab01d1cfc30aebe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
