HTTP 305 Use Proxy — Deprecated Status Code

HTTP 305 Use Proxy is a deprecated status code that instructed clients to access the resource through a specified proxy. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: 305 was defined in RFC 2616 but deprecated due to security concerns. Told clients to re-request the resource through the proxy in the Location header. Modern browsers do not honor this status code. Could be exploited to redirect traffic through malicious proxies. Replaced by explicit proxy configuration or PAC files. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Legacy server configuration from early HTTP/1.1 era. Misconfigured server software sending deprecated status codes. Documentation or testing referencing historical HTTP codes. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: If your server returns 305, update the configuration to use a different approach. Use a reverse proxy (nginx, HAProxy) that is transparent to the client. For client-side proxy requirements, use PAC (Proxy Auto-Config) files. Modern proxy requirements should use 407 Proxy Authentication Required. Remove any 305 configurations from web server settings. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.