Multiple Choices

Overview

300 Multiple Choices means the requested resource has several possible representations, and the client or user must pick one. The server sends it when content negotiation alone cannot automatically choose a single option, so it presents a list of candidates.

For example, when a document exists in multiple languages, formats (HTML/PDF), or resolutions, the server lists the choices in the body or Link headers and lets the user select.

When it happens

• It can be returned for a document with several languages or formats when Accept-family headers cannot pin down exactly one.
• If the server has a preferred representation, it may include a Location header as a hint.

Request / Response example

GET /manual HTTP/1.1
Host: docs.example.com
Accept: text/html

HTTP/1.1 300 Multiple Choices
Content-Type: text/html
Link: </manual.en.html>; rel=alternate; hreflang=en
Link: </manual.ko.html>; rel=alternate; hreflang=ko

<ul><li><a href="/manual.en.html">English</a></li><li><a href="/manual.ko.html">한국어</a></li></ul>

In code

app.get('/manual', (req, res) => {
  res.status(300).json({
    choices: ['/manual.en.html', '/manual.ko.html']
  });
});

Notes

• It is rarely used in practice; most sites negotiate and then redirect with 302/301 to a specific representation, or just answer 200.
• 300 is not an automatic redirect, so browsers do not navigate on their own — usually a human must act on the choice UI.

Related status codes

Related headers

Specification