305 Use Proxy
3xx redirect
The requested resource must be reached through the proxy whose URI is given in the Location header, deprecated in favour of configuring the proxy directly.
Common causes
- A legacy configuration still declares a mandatory forward proxy.
- An enterprise network routes traffic through an egress gateway.
- A mirror setup assumes clients honour the proxy directive.
How to fix it
- Configure the proxy at the client or OS level instead of relying on 305.
- Verify the proxy URI in Location is still live.
- Test with modern browsers before depending on the header.
What it means for redirects and SEO
Deprecated by most browsers, so proxy routing no longer reaches search crawlers through it. Link checkers may flag it as informational. When a chain relies on 305, expect the proxy step to be ignored and verify the final URL resolves directly.
Trace a link that returns 305 →