Devolver un HttpResponse

A view must return an HttpResponse. Django sends that object to the browser, so returning it is not optional. 📤

Pass a string to HttpResponse and Django sends it as the page body. That string becomes what the browser shows.

The body can be full HTML. The browser renders the tags, so you can return markup directly from a simple view.

Give status a number to control the result code. Use 201 for created or 403 for forbidden instead of the default 200.

The content_type tells the browser how to read the body. Switch it to text/plain to send raw text instead of HTML.

Treat the response like a dictionary to add headers. This is how you set things like caching or custom flags.

Call set_cookie on the response to store a value in the browser. It comes back on the next request automatically.

Use delete_cookie to remove one you previously set. The browser drops it and stops sending it back to you.

Create the response, customize it, then return it. You can set status, headers, and cookies before handing it back.

An HttpResponse is a normal Python object. You can adjust it across several lines before the view finally returns it.

Once returned, your response goes back through middleware and out to the user, completing the cycle. ✅

How do you make a view respond with status 201?

An HttpResponse carries the body, status, content type, headers, and cookies. Shape it, then return it. 🎁