Django: What is the difference b/w HttpResponse vs HttpResponseRedirect vs render_to_response

Question

The above mentioned things are giving me almost the same results was wondering whats the main difference in them.

Answer 1

1. response = HttpResponse("Here's the text of the Web page."):
   will create a new HttpResponse object with HTTP code 200 (OK), and the content passed to the constructor. In general, you should only use this for really small responses (like an AJAX form return value, if its really simple - just a number or so).

2. HttpResponseRedirect("http://example.com/"):
   will create a new HttpResponse object with HTTP code 302 (Found/Moved temporarily). This should be used only to redirect to another page (e.g. after successful form POST)

From the docs:

class HttpResponseRedirect The constructor takes a single argument -- the path to redirect to. This can be a fully qualified URL (e.g. 'http://www.yahoo.com/search/') or an absolute URL with no domain (e.g. '/search/'). Note that this returns an HTTP status code 302.

enough said...

render_to_response(template[, dictionary][, context_instance][,mimetype])
Renders a given template with a given context dictionary and returns an HttpResponse object with that rendered text.

is a call to render a template with given dictionary of variables to create the response for you. This is what you should be using most of the time, because you want to keep your presentation logic in templates and not in code.