      If you are deployed behind a load-balancer or reverse-proxy server and
      Django can't seem to tell when a request actually is already secure, you
      may need to set the :setting:`SECURE_PROXY_SSL_HEADER` setting.
  
  .. _nginx: https://nginx.org
  
  Session middleware
  ------------------
  
  .. module:: django.contrib.sessions.middleware
 
</s> remove `Jinja2 <http://jinja.pocoo.org/docs/>`_ can offer performance improvements,
particularly when it comes to speed.
 </s> add Jinja2_ can offer performance improvements, particularly when it comes to
speed. </s> remove     .. _python: https://python.org/
 </s> add     .. _python: https://www.python.org/ </s> remove .. _sqlite: https://sqlite.org/
 </s> add .. _sqlite: https://www.sqlite.org/ </s> remove If you need a web address, use https://djangoproject.com.
 </s> add If you need a web address, use https://www.djangoproject.com/. </s> remove .. _django-users: https://groups.google.com/group/django-users
 </s> add .. _django-users: https://groups.google.com/g/django-users
.. _nginx: https://nginx.org/
      If you are deployed behind a load-balancer or reverse-proxy server and
      Django can't seem to tell when a request actually is already secure, you
      may need to set the :setting:`SECURE_PROXY_SSL_HEADER` setting.
  
.. _nginx: https://nginx.org/
  
  Session middleware
  ------------------
  
  .. module:: django.contrib.sessions.middleware
keep keep keep keep replace keep keep keep keep keep
 Refs #32720 -- Updated various links in docs to avoid redirects and use HTTPS. 
docs/ref/middleware.txt