Middleware order
The order of middleware affections the outcome. Some middleware are dependant on the functionality of other middleware. For example a middleware that requires usage of request.session should come after the SessionMiddleware.
If our GitHub code review bot spots this issue in your pull request it gives this advice:
django-doctorbot just nowsettings.py
1 | + | MIDDLEWARE =[ | |
2 | + | "django.contrib.auth.middleware.AuthenticationMiddleware", | |
3 | + | "django.contrib.sessions.middleware.SessionMiddleware", |
The order of middleware affections the outcome. Some middleware are dependant on the functionality of other middleware. For example a middleware that requires usage of request.session should come after the SessionMiddleware.
Read more4 | + | ... | |
5 | + | ] |
Update settings.pyInstantly check if you have this issue for free
Works with tools you use
- Detect typos
- Avoid mistakes
- Prevent bugs
- Improve tests
- Read more
- Review PRs
- One click fix
- Clear advice
- Delta aware
- Read more
- Review PRs
- Fix suggested
- Clear advice
- Delta aware
- Read more
Read about how it works.