Ticket #9081: flexible_render_to_response.2.diff

django/shortcuts/__init__.py

@@ -11 +11 @@
 
 def render_to_response(*args, **kwargs):
     """
-    Returns a HttpResponse whose content is filled with the result of calling
+    Returns a HttpResponse (or subclass) whose content is filled with the result of calling
     django.template.loader.render_to_string() with the passed arguments.
     """
-    httpresponse_kwargs = {'mimetype': kwargs.pop('mimetype', None)}
-    return HttpResponse(loader.render_to_string(*args, **kwargs), **httpresponse_kwargs)
+    httpresponse_kwargs, response_class = {'mimetype': kwargs.pop('mimetype', None)}, kwargs.pop('response_class', HttpResponse)
+    return response_class(loader.render_to_string(*args, **kwargs), **httpresponse_kwargs)
 
 def _get_queryset(klass):
     """

docs/topics/http/shortcuts.txt

@@ -12 +12 @@
 ========================
 
 ``django.shortcuts.render_to_response`` renders a given template with a given
-context dictionary and returns an ``HttpResponse`` object with that rendered
-text.
+context dictionary and returns an ``HttpResponse`` object, or subclass
+thereof, with that rendered text.
 
 Required arguments
 ------------------
@@ -48 +48 @@
     The MIME type to use for the resulting document. Defaults to the value of
     the :setting:`DEFAULT_CONTENT_TYPE` setting.
 
+``response_class``
+    The response class to return. By default, the response class will be
+    HttpResponse. This is useful for things like returning HTTP status codes
+    other than 200, or adding your own custom functionality to your response,
+    while still retaining the convenience of render_to_response. For instance,
+    if you wish to return HTTP 400 (Bad Request), you may do this::
+
+        return render_to_response('my_template.html',
+                                  my_data_dictionary,
+                                  response_class=HttpResponseBadRequest)
+
 Example
 -------