diff options
| author | Luke Plant <L.Plant.98@cantab.net> | 2015-06-15 11:17:09 +0100 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2015-06-29 08:16:19 -0400 |
| commit | aef2a0ec59301022354c043744a6a2fa13583aa1 (patch) | |
| tree | ad562a7c7c5379594b499e14574e181188a51f10 /docs/howto | |
| parent | 9ed82154bd0bd01c6195942db84302e791ad366f (diff) | |
Fixed #25018 -- Changed simple_tag to apply conditional_escape() to its output.
This is a security hardening fix to help prevent XSS (and incorrect HTML)
for the common use case of simple_tag.
Thanks to Tim Graham for the review.
Diffstat (limited to 'docs/howto')
| -rw-r--r-- | docs/howto/custom-template-tags.txt | 24 |
1 files changed, 22 insertions, 2 deletions
diff --git a/docs/howto/custom-template-tags.txt b/docs/howto/custom-template-tags.txt index c4e414cdb5..adee0f9ffd 100644 --- a/docs/howto/custom-template-tags.txt +++ b/docs/howto/custom-template-tags.txt @@ -441,6 +441,22 @@ A few things to note about the ``simple_tag`` helper function: * If the argument was a template variable, our function is passed the current value of the variable, not the variable itself. +Unlike other tag utilities, ``simple_tag`` passes its output through +:func:`~django.utils.html.conditional_escape` if the template context is in +autoescape mode, to ensure correct HTML and protect you from XSS +vulnerabilities. + +If additional escaping is not desired, you will need to use +:func:`~django.utils.safestring.mark_safe` if you are absolutely sure that your +code does not contain XSS vulnerabilities. For building small HTML snippets, +use of :func:`~django.utils.html.format_html` instead of ``mark_safe()`` is +strongly recommended. + +.. versionchanged:: 1.9 + + Auto-escaping for ``simple_tag`` as described in the previous two paragraphs + was added. + If your template tag needs to access the current context, you can use the ``takes_context`` argument when registering your tag:: @@ -792,12 +808,16 @@ Ultimately, this decoupling of compilation and rendering results in an efficient template system, because a template can render multiple contexts without having to be parsed multiple times. +.. _tags-auto-escaping: + Auto-escaping considerations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The output from template tags is **not** automatically run through the -auto-escaping filters. However, there are still a couple of things you should -keep in mind when writing a template tag. +auto-escaping filters (with the exception of +:meth:`~django.template.Library.simple_tag` as described above). However, there +are still a couple of things you should keep in mind when writing a template +tag. If the ``render()`` function of your template stores the result in a context variable (rather than returning the result in a string), it should take care |
