[1.9.x] Fixed #25804 -- Documented additions to Jinja2 context.

Backport of 6aef986cdbff72809b39880132959ef74827492f from master

1 files changed, 7 insertions, 4 deletions

diff --git a/docs/topics/templates.txt b/docs/topics/templates.txt
index 5e5dee5168..77c3b4ce4c 100644
--- a/docs/topics/templates.txt
+++ b/docs/topics/templates.txt
@@ -456,10 +456,13 @@ adds defaults that differ from Jinja2's for a few options:
 * ``'auto_reload'``: ``settings.DEBUG``
 * ``'undefined'``: ``DebugUndefined if settings.DEBUG else Undefined``
 
-The default configuration is purposefully kept to a minimum. The ``Jinja2``
-backend doesn't create a Django-flavored environment. It doesn't know about
-Django context processors, filters, and tags. In order to use Django-specific
-APIs, you must configure them into the environment.
+The default configuration is purposefully kept to a minimum. If a template is
+rendered with a request (e.g. when using :py:func:`~django.shortcuts.render`),
+the ``Jinja2`` backend adds the globals ``request``, ``csrf_input``, and
+``csrf_token`` to the context. Apart from that, this backend doesn't create a
+Django-flavored environment. It doesn't know about Django context processors,
+filters, and tags. In order to use Django-specific APIs, you must configure
+them into the environment.
 
 For example, you can create ``myproject/jinja2.py`` with this content::