HTTP 305 Use Proxy

Updated October 18, 2026Free mock REST & WebSocket APIs

HTTP 305 Use Proxy — Deprecated: the resource had to be accessed through the proxy in the Location header.

Try it: get a real 305 response

Our test endpoint answers every request with 305 Use Proxy.

curl -i https://mockfox.dev/api/status/305

Use it in tests, health-check monitors or to see how your client handles a 305. Add ?delay=2000 to slow it down.

What does HTTP 305 mean?

Deprecated since RFC 7231 because letting a response configure a proxy for the client was a security risk. Browsers ignore it; never send it.

Visitors: Browsers handle redirects automatically. If you're stuck in a loop, clear the site's cookies and cache.
Developers: Check the Location header and test redirects with curl -I. Prefer 301/308 for permanent moves and 302/303/307 for temporary ones.

HTTP/1.1 305 Use Proxy
Content-Type: application/json

{"status":305,"error":"Use Proxy"}

3xx Redirection: Further action (usually following a Location header) is needed to complete the request. See the full list of HTTP status codes.

What does HTTP 305 Use Proxy mean?

Deprecated: the resource had to be accessed through the proxy in the Location header.

Is 305 an error?

No. 305 is a redirection status — the client needs to take another step, usually following the Location header.

Where is 305 defined?

In RFC 9110 §15.4.6. It's listed in the IANA HTTP Status Code Registry, but marked deprecated or reserved.

How can I test how my app handles a 305?

Call https://mockfox.dev/api/status/305 — it responds with 305 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.