When you see this status
- Proxy or gateway transforms response before forwarding
- Intermediary modifies payload for client-specific needs
- Backend service enriches data before returning to client
Common causes
- Intermediary proxy altering response content
- Caching layer modifying payload metadata
- API gateway transforming data for compatibility
How to debug it
- Inspect proxy/gateway configuration for transformations
- Verify origin server response headers for 200
- Check intermediary logs for modification details
Return this code in your framework
Express (Node.js)
res.status(203).json({ data: 'modified' });
FastAPI (Python)
return JSONResponse(content={'data': 'modified'}, status_code=203)
NestJS
@Get() @HttpCode(203) getData() { return { data: 'modified' }; }
Go (net/http)
w.WriteHeader(http.StatusNonAuthoritativeInfo); w.Write([]byte(`{"data":"modified"}`))
About HTTP 203
HTTP status code 203 Non-Authoritative Information is part of the
2xx Success family. Response contains modified or transformed data from the origin server. 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.