From f95bd89e827d6ee46cc6c736dadc25a10ae25fc9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Tue, 9 Aug 2016 15:06:47 +0300 Subject: [PATCH] Fixed #27041 -- Documented that built-in middleware are compatible with MIDDLEWARE and MIDDLEWARE_CLASSES. --- docs/topics/http/middleware.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/topics/http/middleware.txt b/docs/topics/http/middleware.txt index 1f79256027..3ead020838 100644 --- a/docs/topics/http/middleware.txt +++ b/docs/topics/http/middleware.txt @@ -311,7 +311,8 @@ Upgrading pre-Django 1.10-style middleware Django provides ``django.utils.deprecation.MiddlewareMixin`` to ease creating middleware classes that are compatible with both :setting:`MIDDLEWARE` and the -old :setting:`MIDDLEWARE_CLASSES`. +old :setting:`MIDDLEWARE_CLASSES`. All middleware classes included with Django +are compatible with both settings. The mixin provides an ``__init__()`` method that accepts an optional ``get_response`` argument and stores it in ``self.get_response``.