Multiple Choices

3xx Redirection

Server perspective

Use 300 when more than one representation or target is valid and the client should pick the preferred one.

•Return 300 for reactive negotiation when the response should list alternatives instead of choosing for the client
•If there is a preferred target, you may also include Location to point at that preference

•Include a machine- or human-readable list of alternatives in the response body
•Keep each alternative specific enough that the client can make a meaningful choice

•Include a list of alternative representations or URIs; Location is optional, not mandatory

•Do not use 300 as a generic redirect when there is only one real target
•Do not expect clients to understand an undocumented custom alternatives format automatically

Request:GET /invoice/123

Response:300 Multiple Choices listing HTML, PDF, and JSON variants

The server defers the final representation choice to the client.

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.

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.