WhereGoes

203 Non-Authoritative Information

2xx success

The request succeeded but the returned metadata came from a transforming proxy or local copy rather than directly from the origin, so headers may differ.

Common causes

  • An intermediary rewrote or stripped response headers.
  • A mirror or cache serves a modified copy of the origin response.
  • A legacy proxy adds its own signature to the response.

How to fix it

  • Compare headers at the origin and at the edge to find what the proxy rewrites.
  • Configure the proxy to preserve canonical and robots headers.
  • Bypass the transforming layer for crawl-critical routes.

What it means for redirects and SEO

The proxy-transformed copy may differ from origin, so canonicals and structured data can drift. Crawlers index what the proxy returns, which can split ranking signals from the origin version. Verify headers survive the proxy.

Related codes