HTTP 300 – Multiple Choices
The request has more than one possible response, and the client should choose one.
Common use case
Rarely used directly, but conceptually applies to content-negotiation scenarios where a URL could resolve to several formats (e.g. .json vs .xml) and the server lets the client pick.
Example
HTTP/1.1 300 Multiple Choices
Location: /article.html
History
Defined in the original HTTP/1.1 specification, RFC 2068 (1997).
Did you know?
It is one of the least implemented redirect codes in practice - most servers pick a default representation instead of asking the client to choose.