203 Non-Authoritative Information

The request succeeded, but an intermediary modified the payload it received from the origin server.

Status

HTTP/1.1 203 Non-Authoritative Information

Details

203 is 200 with a disclosure attached: some hop between the origin and the client changed the response. Typical modifications are image recompression by a mobile carrier, script injection by a filtering proxy, or content adaptation by an enterprise gateway.

The code is rare in the wild because most intermediaries that rewrite payloads simply pass the original 200 through without admitting to it. When you do see it, the body is still usable, but it is no longer byte-identical to what the origin sent.

Headers

Common causes

How to fix it

As the client

As the server

Examples

GET /images/hero.jpg HTTP/1.1
Host: www.example.com

HTTP/1.1 203 Non-Authoritative Information
Content-Type: image/jpeg
Content-Length: 18422
Warning: 214 carrier-proxy "Transformation applied"

Notes for proxy users

Seeing 203 while scraping means something in the path is rewriting bodies, which will corrupt content comparisons and hash checks. A dedicated proxy that forwards traffic without transformation avoids the whole class of problem.

Specifications

RFC 9110 §15.3.4

See also