summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/internals/deprecation.txt3
-rw-r--r--docs/ref/request-response.txt21
2 files changed, 13 insertions, 11 deletions
diff --git a/docs/internals/deprecation.txt b/docs/internals/deprecation.txt
index f338adac33..9359c82e46 100644
--- a/docs/internals/deprecation.txt
+++ b/docs/internals/deprecation.txt
@@ -280,6 +280,9 @@ these changes.
specified as a plain string instead of a tuple will be removed and raise an
exception.
+* The ``mimetype`` argument to :class:`~django.http.HttpResponse` ``__init__``
+ will be removed (``content_type`` should be used instead).
+
2.0
---
diff --git a/docs/ref/request-response.txt b/docs/ref/request-response.txt
index a29ddc63cc..551ee00c6b 100644
--- a/docs/ref/request-response.txt
+++ b/docs/ref/request-response.txt
@@ -606,11 +606,10 @@ Attributes
Methods
-------
-.. method:: HttpResponse.__init__(content='', mimetype=None, status=200, content_type=DEFAULT_CONTENT_TYPE)
+.. method:: HttpResponse.__init__(content='', content_type=None, status=200)
- Instantiates an ``HttpResponse`` object with the given page content (a
- string) and MIME type. The :setting:`DEFAULT_CONTENT_TYPE` is
- ``'text/html'``.
+ Instantiates an ``HttpResponse`` object with the given page content and
+ content type.
``content`` should be an iterator or a string. If it's an
iterator, it should return strings, and those strings will be
@@ -618,15 +617,15 @@ Methods
an iterator or a string, it will be converted to a string when
accessed.
+ ``content_type`` is the MIME type optionally completed by a character set
+ encoding and is used to fill the HTTP ``Content-Type`` header. If not
+ specified, it is formed by the :setting:`DEFAULT_CONTENT_TYPE` and
+ :setting:`DEFAULT_CHARSET` settings, by default: "`text/html; charset=utf-8`".
+
+ Historically, this parameter was called ``mimetype`` (now deprecated).
+
``status`` is the `HTTP Status code`_ for the response.
- ``content_type`` is an alias for ``mimetype``. Historically, this parameter
- was only called ``mimetype``, 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, the
- :setting:`DEFAULT_CONTENT_TYPE` setting is used.
.. method:: HttpResponse.__setitem__(header, value)