Ticket #8538: middleware_warnings.patch

docs/topics/http/middleware.txt

@@ -111 +111 @@
 object. It could alter the given ``response``, or it could create and return a
 brand-new :class:`~django.http. HttpResponse`.
 
+Like ``process_request()`` and ``process_view()`` above, it is important to
+understand that your middleware will not be called if another middleware
+object returns a response before you.  But unlike ``process_request()`` and 
+``process_view()`` the classes are applied in reverse order, from the bottom 
+up.  This means classes defined towards the end of 
+:setting:`MIDDLEWARE_CLASSES` will go first.
+
 .. _exception-middleware:
 
 ``process_exception``
@@ -127 +134 @@
 :class:`~django.http. HttpResponse` object, the response will be returned to
 the browser. Otherwise, default exception handling kicks in.
 
+Again, remember that because middelware classes are applied in reverse order
+for ``process_exception``, classes defined towards the end of 
+:setting:`MIDDLEWARE_CLASSES` will go first, and if any return a
+response, the middleware classes above it will not be called at all.
+
 ``__init__``
 ------------