TrueURL

305 Use Proxy

Deprecated. Told the client to repeat the request through the proxy given in Location; browsers ignore it for security reasons.

Reason phrase
Use Proxy
Redirect
No
Cacheable by default
No

305 Use Proxy was defined in HTTP/1.1 to tell a client that the resource must be accessed through the proxy whose URL is given in the Location header. Letting any website tell a client which proxy to use is dangerous, because an attacker could route the client's traffic through a proxy under their control.

RFC 7231 deprecated 305 in 2014, and RFC 9110 keeps it only as a deprecated registration. Browsers and current HTTP libraries do not act on it: they show the response or treat it as an error.

Example response

HTTP
HTTP/1.1 305 Use Proxy
Date: Fri, 06 Nov 2026 10:15:32 GMT
Location: http://proxy.example.net:8080/
Content-Length: 0

SEO and redirect checking

305 has no valid use on the web today. If a redirect check shows a 305, the server or a device in front of it is misconfigured or very old. Crawlers do not follow it, so the content behind it cannot be indexed.

Common causes and use cases

  • Legacy server software or a misconfigured proxy still sends 305.
  • A custom application uses 305 instead of a real redirect. Replace it with 302, 307 or a proper proxy setup.
  • A network that requires a proxy should configure it through system settings or proxy auto-configuration (PAC/WPAD) instead.

URL Redirect Checker

See every status code a URL returns, hop by hop, with the free TrueURL redirect checker.