Unused

3xx Redirection

Server perspective

Do not emit 306; it is reserved and has no defined modern behavior.

•Audit any code path that returns 306 because it likely indicates a bug, placeholder, or undocumented custom behavior
•Map the response to a defined HTTP status that matches the actual semantics

•No status-specific header is defined because 306 has no active modern semantics.

•There is no defined response body contract for 306 because there is no active status semantics to implement

Request:Service returns 306 from an error path

Response:Replace it with a defined 3xx, 4xx, or 5xx status that matches the real outcome

A reserved code hides intent and breaks interoperability.

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 is an old HTTP idea that said, 'Use this proxy instead,' but modern systems should not rely on it.

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.