Use Proxy

3xx Redirection

Server perspective

Do not emit 305 in modern systems; keep it as historical reference material only.

•Avoid 305 for real application behavior because it is deprecated and unsafe as a proxy-configuration signal
•Use explicit proxy setup or ordinary redirect codes instead of trying to steer clients through a proxy this way

•If you maintain a legacy component that still knows about 305, plan to remove or replace that behavior
•Do not introduce new 305 responses in APIs, gateways, or web applications

•No modern product flow should depend on a 305 response body; the historical proxy target was carried in Location

Request:Old gateway considers replying with 305

Response:Replace the design with explicit proxy configuration or a supported redirect pattern

The right fix is to remove the deprecated behavior, not document it as an active contract.

There are several valid versions of this thing, and the server is asking you to pick one.

This moved for good. Start using the new address from now on.

Go somewhere else for now, but don’t assume this new address is the permanent one.

You submitted something successfully. Now go fetch this other page to see the result.

You already have the latest version! The thing you're asking for hasn't changed since you last got it.

This number exists in the HTTP list, but it does not mean anything you should use in a real app today.

Go to this other address for now, and send the exact same kind of request there.

This moved for good, and you should keep using the same kind of request when you switch to the new address.