2xx Success
HTTP 203 Non-Authoritative Information
The request was successful but the returned metadata may be from a local or third-party copy rather than the origin server. This is mostly used by mirrors or backups of another resource.
Common Causes
- Response modified by a transforming proxy
- Cached copy served from a CDN with modified headers
- Mirror server returning slightly different metadata
How to Fix
- 1No fix needed if the data is acceptable
- 2Request directly from the origin server for authoritative data
- 3Check proxy and CDN configuration if metadata accuracy matters
Example
HTTP 203 Non-Authoritative Information
GET /api/data HTTP/1.1 → 203 Non-Authoritative Information → Data may differ from the origin server's version