HTTP 226 IM Used — Delta Encoding Applied
Informational2xx success
Overview
HTTP 226 IM Used indicates the server applied instance manipulations (delta encoding) to the response as requested by the client.
Key Details
- Defined in RFC 3229 for delta encoding in HTTP
- The response is a delta (difference) from a previous version
- Reduces bandwidth by sending only changes instead of the full resource
- The A-IM header specifies the instance manipulation type (vcdiff, diffe, etc)
- Rarely implemented in practice despite being standardized
Common Causes
- Client sent A-IM header requesting delta encoding
- Server supports instance manipulations and applied them
- Feed aggregator using delta encoding for efficient updates
Steps
- 1No fix needed — 226 indicates successful delta response
- 2If developing a client, apply the delta to your cached version to reconstruct the full resource
- 3The response includes IM: header specifying which manipulation was applied
- 4If you want the full resource, omit the A-IM header in your request
- 5Test your delta decoding logic against the full resource for correctness
Tags
http226delta-encodingim-usedbandwidth
More in 2xx Success
http-200-okHTTP 200 OK — What It Means & How to Fix It
Informationalhttp-201-createdHTTP 201 Created — What It Means & How to Fix It
Informationalhttp-202-acceptedHTTP 202 Accepted — What It Means & How to Fix It
Informationalhttp-203-non-authoritative-informationHTTP 203 Non-Authoritative Information — What It Means & How to Fix It
Informationalhttp-204-no-contentHTTP 204 No Content — What It Means & How to Fix It
Informationalhttp-205-reset-contentHTTP 205 Reset Content — What It Means & How to Fix It
InformationalFrequently Asked Questions
No. Very few servers implement delta encoding. Most use compression (gzip/brotli) and conditional requests (ETags) instead.