ส่งสตริง HTML และรหัสสถานะ

The simplest response is a plain string. Flask sends it straight to the browser as the page body with a 200 status.

Your string can contain real HTML tags. The browser parses them, so returning a heading renders as a styled title, not as raw text.

Writing big pages as one giant string gets unreadable fast. It works for tiny snippets, but real pages belong in template files later.

When you return just a body, Flask assumes a 200 status, meaning OK. You only set a code when the result is not a plain success.

Return a tuple of body and number to set the status. Here a missing item answers with a 404 instead of the default 200.

Use 201 when you create something new and 200 for a normal read. The right code tells clients exactly what happened.

Use 400 for bad input, 404 for missing pages, and 500 when your own code crashes. Each number has a clear, agreed meaning.

Extend the tuple with a third part, a dict of headers, when you need to control things like the content type of the reply.

For finer control, build a make_response object. You can set its status and headers step by step before returning it.

Even a bare string gets wrapped in a full response behind the scenes. Flask handles the boilerplate so your views stay short.

Always return a truthful status. Sending 200 for an error confuses clients and hides real bugs from anyone using your app.

Pick the response that sets a custom status.

You can return plain text, HTML, or a tuple with a status and headers. Honest status codes keep your responses clear and trustworthy. ✅