HTTP · 2xx Success

205 Reset Content

Server instructs client to reset the document view without loading a new resource.

When you see this status

Client submits a form and server clears form fields
Client requests a document reset after POST
Server clears UI state after successful action

Common causes

Client expects UI reset after server-side action
Server processes action but no new content to return
Client requests document reset explicitly

How to debug it

Verify client handles 205 by resetting UI state
Check server sends no response body with 205
Ensure client does not cache 205 responses

Return this code in your framework

Express (Node.js)

res.status(205).send();

FastAPI (Python)

@app.post('/reset')
async def reset():
    return Response(status_code=205)

NestJS

@Get('reset')
reset() {
  return new HttpResponse('Reset', 205);
}

Go (net/http)

w.WriteHeader(http.StatusResetContent)

About HTTP 205

HTTP status code 205 Reset Content is part of the 2xx Success family. Server instructs client to reset the document view without loading a new resource. Understanding it is essential for backend engineers, API designers, and anyone debugging integrations between services.

The Qaynaq Labs HTTP Status Code Explainer covers all standard codes with practical guidance: what triggers them, how to debug them in production, and exactly how to return them from common frameworks. Each code page is hand-curated and verified.

Frequently asked

Does 205 require a response body?

No, 205 must not include a response body. The client should reset the view based on headers only.

When should I use 205 vs 204?

Use 205 when the client should reset the document view. Use 204 when no UI change is needed.

Can browsers handle 205 responses?

Most modern browsers reset form fields on 205, but behavior is not standardized across all clients.