HTTP 226 IM Used — Delta Encoding Applied

HTTP 226 IM Used indicates the server applied instance manipulations (delta encoding) to the response as requested by the client. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: 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. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Client sent A-IM header requesting delta encoding. Server supports instance manipulations and applied them. Feed aggregator using delta encoding for efficient updates. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: No fix needed — 226 indicates successful delta response. If developing a client, apply the delta to your cached version to reconstruct the full resource. The response includes IM: header specifying which manipulation was applied. If you want the full resource, omit the A-IM header in your request. Test your delta decoding logic against the full resource for correctness. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.