When you see this status
- Client sends If-None-Match with 'A-IM: vcdiff' header
- Server supports delta encoding and applies changes to previous response
- Response body contains only the differences from prior representation
Common causes
- Client explicitly requests delta encoding via A-IM header
- Server supports delta encoding (e.g., vcdiff, gzip)
- Resource has been modified since last request
How to debug it
- Verify client sent 'A-IM: vcdiff' or similar in request
- Check server logs for delta encoding support
- Inspect response headers for 'ETag' and 'Delta-Base'
- Validate response body contains only deltas
Return this code in your framework
Express (Node.js)
res.status(226).set('A-IM', 'vcdiff').send(deltaBuffer);
FastAPI (Python)
return Response(content=delta, status_code=226, headers={"A-IM": "vcdiff"})
NestJS
@Get() getWithDelta(@Res() res: Response) { res.status(226).set('A-IM', 'vcdiff').send(delta); }
Go (net/http)
w.WriteHeader(http.StatusIMUsed); w.Header().Set("A-IM", "vcdiff"); w.Write(delta)
About HTTP 226
HTTP status code 226 IM Used is part of the
2xx Success family. Server fulfilled request using a delta encoding of the response. 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.