| 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.
Modern clients should not implement 305 as an instruction to route the request through the URI supplied by an untrusted response. The status was deprecated because of security concerns around proxy configuration. If it appears in old software, treat it as legacy behavior and verify the intended proxy configuration independently.
Looking for a different code? Search another status or error code.
