Fixed #26452 -- Loaded middleware on server start rather than on first request.

2 files changed, 9 insertions, 2 deletions

diff --git a/docs/releases/1.10.txt b/docs/releases/1.10.txt
index fc155735dc..96b9d23f62 100644
--- a/docs/releases/1.10.txt
+++ b/docs/releases/1.10.txt
@@ -714,6 +714,9 @@ Miscellaneous
   :class:`~django.contrib.postgres.fields.RangeField`, you should change the
   ``base_field`` attribute.
 
+* Middleware classes are now initialized when the server starts rather than
+  during the first request.
+
 .. _deprecated-features-1.10:
 
 Features deprecated in 1.10
diff --git a/docs/topics/http/middleware.txt b/docs/topics/http/middleware.txt
index e84aafa123..16fdace825 100644
--- a/docs/topics/http/middleware.txt
+++ b/docs/topics/http/middleware.txt
@@ -260,8 +260,12 @@ of caveats:
   define ``__init__`` as requiring any arguments.
 
 * Unlike the ``process_*`` methods which get called once per request,
-  ``__init__`` gets called only *once*, when the Web server responds to the
-  first request.
+  ``__init__`` gets called only *once*, when the Web server starts.
+
+.. versionchanged:: 1.10
+
+    In older versions, ``__init__`` was not called until the Web server
+    responded to its first request.
 
 Marking middleware as unused
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~