205 Reset Content
The request worked and the client should reset the document view, such as clearing the form the user just submitted.
What 205 Reset Content means
Like 204, a 205 has no body. It also asks the client to reset the view that sent the request, for example clearing form fields so the user can enter another record.
Browsers do not reliably act on it, so most apps clear forms in JavaScript and send 204 or 200 instead.
Example response
HTTP/1.1 205 Reset Content
Content-Type: text/plain; charset=utf-8
205 Reset ContentHow to check for a 205 response
cURL
# Print only the status code
curl -s -o /dev/null -w "%{http_code}\n" https://example.com/JavaScript (Node.js)
const res = await fetch("https://example.com/");
if (res.status === 205) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 205:
print(res.status_code, res.reason)Go
res, err := http.Get("https://example.com/")
if err != nil {
log.Fatal(err)
}
defer res.Body.Close()
if res.StatusCode == 205 {
fmt.Println(res.Status)
}Specification
205 Reset Content is defined in RFC 9110, section 15.3.6.
Related status codes
- 204
The request worked and there is nothing to send back. The response has no body, and the browser stays on the current page.
- 200
The request worked. The response body holds the result, such as the page, file or JSON data the client asked for.