      ``content_type``
  
          .. versionchanged:: 1.5
  
          Historically, this parameter was only called ``mimetype`` (now
          deprecated), but since this is actually the value included in the HTTP
          ``Content-Type`` header, it can also include the character set
          encoding, which makes it more than just a MIME type specification. If
          ``mimetype`` is specified (not ``None``), that value is used.
          Otherwise, ``content_type`` is used. If neither is given,
          :setting:`DEFAULT_CONTENT_TYPE` is used.
  
  
  .. method:: SimpleTemplateResponse.resolve_context(context)
  
      Converts context data into a context instance that can be used for
 
</s> remove When the :func:`atomic` decorator is nested, it creates a savepoint to allow
partial commit or rollback. You're strongly encouraged to use :func:`atomic`
rather than the functions described below, but they're still part of the
public API, and there's no plan to deprecate them.
 </s> add     When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them. </s> remove             The ``content_type`` attribute was added.
 </s> add  </s> remove The current value of the field will be displayed as a clickable link above the
input widget.
 </s> add     The current value of the field will be displayed as a clickable link above the
    input widget. </s> remove   Previously Django used ``SELECT`` - if not found ``INSERT`` else ``UPDATE``
  algorithm. The old algorithm resulted in one more query in ``UPDATE`` case.
 </s> add     Previously Django used ``SELECT`` - if not found ``INSERT`` else ``UPDATE``
    algorithm. The old algorithm resulted in one more query in ``UPDATE`` case. </s> remove Django used to remove the ``cleaned_data`` attribute entirely if there were
any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
the form doesn't validate, but it contains only field values that did
validate.
 </s> add     Django used to remove the ``cleaned_data`` attribute entirely if there were
    any errors in the form. Since version 1.5, ``cleaned_data`` is present even if
    the form doesn't validate, but it contains only field values that did
    validate.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
      ``content_type``
  
          .. versionchanged:: 1.5
  
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
            Historically, this parameter was only called ``mimetype`` (now
            deprecated), but since this is actually the value included in the HTTP
            ``Content-Type`` header, it can also include the character set
            encoding, which makes it more than just a MIME type specification. If
            ``mimetype`` is specified (not ``None``), that value is used.
            Otherwise, ``content_type`` is used. If neither is given,
            :setting:`DEFAULT_CONTENT_TYPE` is used.
  
  
  .. method:: SimpleTemplateResponse.resolve_context(context)
  
      Converts context data into a context instance that can be used for
keep keep keep keep replace replace replace replace replace replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/ref/template-response.txt