| Previous | Next |
| HTTP_STATUS_NOT_MODIFIED | HTTP_STATUS_SWITCH_PROXY |
HTTP_STATUS_USE_PROXY
Current HTTP specifications mark 305 as deprecated because proxy configuration through a response can create security and interoperability problems. Modern applications should use explicit network configuration or documented redirect behavior instead.
If a legacy system returns 305, inspect the product documentation and proxy policy rather than automatically switching transport endpoints based on the response.
Operational meaning of HTTP 305 for HTTP_STATUS_USE_PROXY
HTTP 305 (HTTP_STATUS_USE_PROXY) is a redirection response. AllStat records its meaning as “305 Use Proxy”. For HTTP_STATUS_USE_PROXY, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_USE_PROXY
- Apply the method-rewrite and caching rules defined for HTTP_STATUS_USE_PROXY, not a generic redirect rule.
- For HTTP_STATUS_USE_PROXY, validate the Location target and prevent redirect loops across proxies or canonicalization layers.
- For HTTP_STATUS_USE_PROXY, log the original URL, target URL, method, and cache decision.
For telemetry, record HTTP 305, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.