203 Non-Authoritative Information
The request worked, but a proxy between you and the origin server changed the response before passing it on.
What 203 Non-Authoritative Information means
A transforming proxy sends 203 when it has modified a 200 response from the origin, for example by recompressing images or rewriting content.
It warns the client that the content is not exactly what the origin sent. You will rarely see it in practice.
Example response
HTTP/1.1 203 Non-Authoritative Information
Content-Type: text/plain; charset=utf-8
203 Non-Authoritative InformationHow to check for a 203 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 === 203) {
console.log(res.status, res.statusText);
}Python
import requests
res = requests.get("https://example.com/")
if res.status_code == 203:
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 == 203 {
fmt.Println(res.Status)
}Specification
203 Non-Authoritative Information is defined in RFC 9110, section 15.3.4.
Related status codes
- 200
The request worked. The response body holds the result, such as the page, file or JSON data the client asked for.
- 304
The cached copy is still valid, so the server sends no body and the client loads the resource from its own cache.