template-response.txt 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307
  1. ===================================================
  2. ``TemplateResponse`` and ``SimpleTemplateResponse``
  3. ===================================================
  4. .. module:: django.template.response
  5. :synopsis: Classes dealing with lazy-rendered HTTP responses.
  6. Standard :class:`~django.http.HttpResponse` objects are static structures.
  7. They are provided with a block of pre-rendered content at time of
  8. construction, and while that content can be modified, it isn't in a form that
  9. makes it easy to perform modifications.
  10. However, it can sometimes be beneficial to allow decorators or
  11. middleware to modify a response *after* it has been constructed by the
  12. view. For example, you may want to change the template that is used,
  13. or put additional data into the context.
  14. TemplateResponse provides a way to do just that. Unlike basic
  15. :class:`~django.http.HttpResponse` objects, TemplateResponse objects retain
  16. the details of the template and context that was provided by the view to
  17. compute the response. The final output of the response is not computed until
  18. it is needed, later in the response process.
  19. ``SimpleTemplateResponse`` objects
  20. ==================================
  21. .. class:: SimpleTemplateResponse()
  22. Attributes
  23. ----------
  24. .. attribute:: SimpleTemplateResponse.template_name
  25. The name of the template to be rendered. Accepts a backend-dependent
  26. template object (such as those returned by
  27. :func:`~django.template.loader.get_template()`), the name of a template,
  28. or a list of template names.
  29. Example: ``['foo.html', 'path/to/bar.html']``
  30. .. attribute:: SimpleTemplateResponse.context_data
  31. The context data to be used when rendering the template. It must be a
  32. :class:`dict`.
  33. Example: ``{'foo': 123}``
  34. .. attribute:: SimpleTemplateResponse.rendered_content
  35. The current rendered value of the response content, using the current
  36. template and context data.
  37. .. attribute:: SimpleTemplateResponse.is_rendered
  38. A boolean indicating whether the response content has been rendered.
  39. Methods
  40. -------
  41. .. method:: SimpleTemplateResponse.__init__(template, context=None, content_type=None, status=None, charset=None, using=None, headers=None)
  42. Instantiates a :class:`~django.template.response.SimpleTemplateResponse`
  43. object with the given template, context, content type, HTTP status, and
  44. charset.
  45. ``template``
  46. A backend-dependent template object (such as those returned by
  47. :func:`~django.template.loader.get_template()`), the name of a template,
  48. or a list of template names.
  49. ``context``
  50. A :class:`dict` of values to add to the template context. By default,
  51. this is an empty dictionary.
  52. ``content_type``
  53. The value included in the HTTP ``Content-Type`` header, including the
  54. MIME type specification and the character set encoding. If
  55. ``content_type`` is specified, then its value is used. Otherwise,
  56. ``'text/html'`` is used.
  57. ``status``
  58. The HTTP status code for the response.
  59. ``charset``
  60. The charset in which the response will be encoded. If not given it will
  61. be extracted from ``content_type``, and if that is unsuccessful, the
  62. :setting:`DEFAULT_CHARSET` setting will be used.
  63. ``using``
  64. The :setting:`NAME <TEMPLATES-NAME>` of a template engine to use for
  65. loading the template.
  66. ``headers``
  67. A :class:`dict` of HTTP headers to add to the response.
  68. .. method:: SimpleTemplateResponse.resolve_context(context)
  69. Preprocesses context data that will be used for rendering a template.
  70. Accepts a :class:`dict` of context data. By default, returns the same
  71. :class:`dict`.
  72. Override this method in order to customize the context.
  73. .. method:: SimpleTemplateResponse.resolve_template(template)
  74. Resolves the template instance to use for rendering. Accepts a
  75. backend-dependent template object (such as those returned by
  76. :func:`~django.template.loader.get_template()`), the name of a template,
  77. or a list of template names.
  78. Returns the backend-dependent template object instance to be rendered.
  79. Override this method in order to customize template loading.
  80. .. method:: SimpleTemplateResponse.add_post_render_callback()
  81. Add a callback that will be invoked after rendering has taken
  82. place. This hook can be used to defer certain processing
  83. operations (such as caching) until after rendering has occurred.
  84. If the :class:`~django.template.response.SimpleTemplateResponse`
  85. has already been rendered, the callback will be invoked
  86. immediately.
  87. When called, callbacks will be passed a single argument -- the
  88. rendered :class:`~django.template.response.SimpleTemplateResponse`
  89. instance.
  90. If the callback returns a value that is not ``None``, this will be
  91. used as the response instead of the original response object (and
  92. will be passed to the next post rendering callback etc.)
  93. .. method:: SimpleTemplateResponse.render()
  94. Sets ``response.content`` to the result obtained by
  95. :attr:`SimpleTemplateResponse.rendered_content`, runs all post-rendering
  96. callbacks, and returns the resulting response object.
  97. ``render()`` will only have an effect the first time it is called. On
  98. subsequent calls, it will return the result obtained from the first call.
  99. ``TemplateResponse`` objects
  100. ============================
  101. .. class:: TemplateResponse()
  102. ``TemplateResponse`` is a subclass of
  103. :class:`~django.template.response.SimpleTemplateResponse` that knows about
  104. the current :class:`~django.http.HttpRequest`.
  105. Methods
  106. -------
  107. .. method:: TemplateResponse.__init__(request, template, context=None, content_type=None, status=None, charset=None, using=None, headers=None)
  108. Instantiates a :class:`~django.template.response.TemplateResponse` object
  109. with the given request, template, context, content type, HTTP status, and
  110. charset.
  111. ``request``
  112. An :class:`~django.http.HttpRequest` instance.
  113. ``template``
  114. A backend-dependent template object (such as those returned by
  115. :func:`~django.template.loader.get_template()`), the name of a template,
  116. or a list of template names.
  117. ``context``
  118. A :class:`dict` of values to add to the template context. By default,
  119. this is an empty dictionary.
  120. ``content_type``
  121. The value included in the HTTP ``Content-Type`` header, including the
  122. MIME type specification and the character set encoding. If
  123. ``content_type`` is specified, then its value is used. Otherwise,
  124. ``'text/html'`` is used.
  125. ``status``
  126. The HTTP status code for the response.
  127. ``charset``
  128. The charset in which the response will be encoded. If not given it will
  129. be extracted from ``content_type``, and if that is unsuccessful, the
  130. :setting:`DEFAULT_CHARSET` setting will be used.
  131. ``using``
  132. The :setting:`NAME <TEMPLATES-NAME>` of a template engine to use for
  133. loading the template.
  134. ``headers``
  135. A :class:`dict` of HTTP headers to add to the response.
  136. The rendering process
  137. =====================
  138. Before a :class:`~django.template.response.TemplateResponse` instance can be
  139. returned to the client, it must be rendered. The rendering process takes the
  140. intermediate representation of template and context, and turns it into the
  141. final byte stream that can be served to the client.
  142. There are three circumstances under which a ``TemplateResponse`` will be
  143. rendered:
  144. * When the ``TemplateResponse`` instance is explicitly rendered, using
  145. the :meth:`SimpleTemplateResponse.render()` method.
  146. * When the content of the response is explicitly set by assigning
  147. ``response.content``.
  148. * After passing through template response middleware, but before
  149. passing through response middleware.
  150. A ``TemplateResponse`` can only be rendered once. The first call to
  151. :meth:`SimpleTemplateResponse.render` sets the content of the response;
  152. subsequent rendering calls do not change the response content.
  153. However, when ``response.content`` is explicitly assigned, the
  154. change is always applied. If you want to force the content to be
  155. re-rendered, you can reevaluate the rendered content, and assign
  156. the content of the response manually:
  157. .. code-block:: pycon
  158. # Set up a rendered TemplateResponse
  159. >>> from django.template.response import TemplateResponse
  160. >>> t = TemplateResponse(request, "original.html", {})
  161. >>> t.render()
  162. >>> print(t.content)
  163. Original content
  164. # Re-rendering doesn't change content
  165. >>> t.template_name = "new.html"
  166. >>> t.render()
  167. >>> print(t.content)
  168. Original content
  169. # Assigning content does change, no render() call required
  170. >>> t.content = t.rendered_content
  171. >>> print(t.content)
  172. New content
  173. Post-render callbacks
  174. ---------------------
  175. Some operations -- such as caching -- cannot be performed on an
  176. unrendered template. They must be performed on a fully complete and
  177. rendered response.
  178. If you're using middleware, you can do that. Middleware provides
  179. multiple opportunities to process a response on exit from a view. If
  180. you put behavior in the response middleware, it's guaranteed to execute
  181. after template rendering has taken place.
  182. However, if you're using a decorator, the same opportunities do not
  183. exist. Any behavior defined in a decorator is handled immediately.
  184. To compensate for this (and any other analogous use cases),
  185. :class:`TemplateResponse` allows you to register callbacks that will
  186. be invoked when rendering has completed. Using this callback, you can
  187. defer critical processing until a point where you can guarantee that
  188. rendered content will be available.
  189. To define a post-render callback, define a function that takes
  190. a single argument -- response -- and register that function with
  191. the template response::
  192. from django.template.response import TemplateResponse
  193. def my_render_callback(response):
  194. # Do content-sensitive processing
  195. do_post_processing()
  196. def my_view(request):
  197. # Create a response
  198. response = TemplateResponse(request, "mytemplate.html", {})
  199. # Register the callback
  200. response.add_post_render_callback(my_render_callback)
  201. # Return the response
  202. return response
  203. ``my_render_callback()`` will be invoked after the ``mytemplate.html``
  204. has been rendered, and will be provided the fully rendered
  205. :class:`TemplateResponse` instance as an argument.
  206. If the template has already been rendered, the callback will be
  207. invoked immediately.
  208. Using ``TemplateResponse`` and ``SimpleTemplateResponse``
  209. =========================================================
  210. A :class:`TemplateResponse` object can be used anywhere that a normal
  211. :class:`django.http.HttpResponse` can be used. It can also be used as an
  212. alternative to calling :func:`~django.shortcuts.render()`.
  213. For example, the following view returns a :class:`TemplateResponse` with a
  214. template and a context containing a queryset::
  215. from django.template.response import TemplateResponse
  216. def blog_index(request):
  217. return TemplateResponse(
  218. request, "entry_list.html", {"entries": Entry.objects.all()}
  219. )