| Previous | Next |
| HTTP_STATUS_IM_USED | HTTP_STATUS_MOVED |
HTTP_STATUS_AMBIGUOUS
The response can provide a list of choices, such as different formats, languages, or alternate resources. Modern servers often choose a more specific redirect or content-negotiation strategy instead of returning 300 directly.
Clients should use the response representation or documented selection policy rather than guessing from the status alone. A 300 response is cacheable by default unless cache controls state otherwise.
For interactive clients, the response can present the alternatives and let the user choose. Automated clients should not guess when several targets are possible unless the application defines a selection rule. If the server has a preferred alternative, it can identify that choice with response metadata rather than forcing clients to infer it.
Looking for a different code? Search another status or error code.