parent
3668da8de8
commit
7fffdc4aad
|
@ -169,5 +169,5 @@ creating an object that specifies the following attributes:
|
|||
* ``'loader_name'``: An optional string identifying the function or class used
|
||||
to load the template, e.g. ``django.template.loaders.filesystem.Loader``.
|
||||
|
||||
.. _DEP 182: https://github.com/django/deps/blob/master/final/0182-multiple-template-engines.rst
|
||||
.. _DEP 182: https://github.com/django/deps/blob/main/final/0182-multiple-template-engines.rst
|
||||
.. _Django Debug Toolbar: https://github.com/jazzband/django-debug-toolbar
|
||||
|
|
|
@ -46,7 +46,7 @@ New-style middleware
|
|||
:doc:`A new style of middleware is introduced </topics/http/middleware>` to
|
||||
solve the lack of strict request/response layering of the old-style of
|
||||
middleware described in `DEP 0005
|
||||
<https://github.com/django/deps/blob/master/final/0005-improved-middleware.rst>`_.
|
||||
<https://github.com/django/deps/blob/main/final/0005-improved-middleware.rst>`_.
|
||||
You'll need to :ref:`adapt old, custom middleware <upgrading-middleware>` and
|
||||
switch from the ``MIDDLEWARE_CLASSES`` setting to the new :setting:`MIDDLEWARE`
|
||||
setting to take advantage of the improvements.
|
||||
|
|
Loading…
Reference in New Issue