📢
203
Non-Authoritative Information

Example HTTP Response

HTTP Response
HTTP/1.1 203 Non-Authoritative Information
Content-Type: application/json

{"data": "modified by proxy"}
Common Causes
  • Response modified by a proxy or cache
  • Metadata from local or third-party copy
  • Mirror or CDN serving transformed content
Technical Details

What does this mean?

It's like getting news through a friend of a friend. The info is good, but it might have been paraphrased along the way!

Technical Definition

The request was successful but the enclosed payload has been modified by a transforming proxy from the origin server's 200 OK response.

RFC Says

"The 203 (Non-Authoritative Information) status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy."

Plain English:

The request was successful, but the response was modified by a proxy or intermediary. This is like receiving information that's been filtered or transformed - it's still valid, just not the original.

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(203).json({
    error: 'Non-Authoritative Information',
    message: 'Your error message here'
  });
});

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

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