SiteError.comYour friendly guide to HTTP status codes
Status CodesBlog
  1. Home
  2. 2xx Success
  3. 226 IM Used

226 IM Used

♻️
226
IM Used
✨
✨

Example HTTP Response

HTTP Response
HTTP/1.1 226 IM Used
IM: delta
Delta-Base: "abc123"
Common Causes
  • Delta encoding applied to response
  • Instance manipulation requested via A-IM header
  • Bandwidth optimization for large resources
Technical Details

What does this mean?

Here's the diff! Instead of sending the whole thing again, the server is sending just what changed. Efficient and eco-friendly!

Technical Definition

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

RFC Says

"The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance."

Plain English:

The server applied transformations (Instance Manipulations) to the resource before sending it. Used with delta encoding to send only changes instead of the full resource, saving bandwidth for frequently updated large resources.

View RFC Documentation
Code Snippets

Ready-to-use code for returning this HTTP status in your application:

Node.js
// Express.js
app.get('/example', (req, res) => {
  res.status(226).json({
    error: 'IM Used',
    message: 'Your error message here'
  });
});

// Native HTTP
const http = require('http');

http.createServer((req, res) => {
  res.writeHead(226, { 'Content-Type': 'application/json' });
  res.end(JSON.stringify({
    error: 'IM Used',
    message: 'Your error message here'
  }));
}).listen(3000);

226 IM Used FAQ

What causes a 226 IM Used error?

Delta encoding applied to response. Instance manipulation requested via A-IM header. Bandwidth optimization for large resources.

208 Already Reported300 Multiple Choices

Popular Status Codes

  • 200 OK
  • 301 Moved Permanently
  • 302 Found
  • 400 Bad Request
  • 401 Unauthorized
  • 403 Forbidden
  • 404 Not Found
  • 500 Internal Server Error
  • 502 Bad Gateway
  • 503 Service Unavailable

Compare Codes

  • 401 vs 403
  • 301 vs 302
  • 404 vs 410
  • 500 vs 502
  • Compare any codes →

Categories

  • Informational
  • Success
  • Redirection
  • Client Error
  • Server Error
  • NGINX
  • Cloudflare
  • AWS ELB
  • Microsoft IIS

Tools

  • Cheat Sheet
  • Status Code Quiz
  • URL Checker
  • API Playground
  • Blog

© 2026 SiteError.com. All rights reserved.