:synopsis: Serving of large files via handler-specific mechanisms.
There are cases when you may wish to serve files in a response, but only want
to provide access to them through your application. As discussed in :ref:`the how-to for serving static
files <howto-static-files>`, Django is not tuned at all for this sort of serving. Thus,
Otherwise, ``content_type`` is used. If neither is given, the
``DEFAULT_CONTENT_TYPE`` setting is used.
``request`` is the request that triggered this response. It can be used in
the event that a view cares about dealing with request headers, in
particular the Accept-Charset header.
.. class:: HttpResponseSendFile
A special response class for efficient file serving. It informs the HTTP
protocol handler to use platform-specific file serving mechanism (if
.. class:: HttpResponseStreaming
A special response class that does not consume generators before returning
the response. To do this, it bypasses middleware that is not useful for
If not ``None``, this defines the header that an :func:`~django.http.HttpResponseSendFile`
-.. function:: render_to_response(template[, dictionary][, context_instance][, mimetype, content_type,
+.. function:: render_to_response(template[, dictionary][, context_instance][, mimetype, content_type, ])
Renders a given template with a given context dictionary and returns an
:class:`~django.http.HttpResponse` object with that rendered text.