| 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.
Operational meaning of HTTP 300 for HTTP_STATUS_AMBIGUOUS
HTTP 300 (HTTP_STATUS_AMBIGUOUS) is a redirection response. AllStat records its meaning as “300 Multiple Choices”. For HTTP_STATUS_AMBIGUOUS, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_AMBIGUOUS
- Apply the method-rewrite and caching rules defined for HTTP_STATUS_AMBIGUOUS, not a generic redirect rule.
- For HTTP_STATUS_AMBIGUOUS, validate the Location target and prevent redirect loops across proxies or canonicalization layers.
- For HTTP_STATUS_AMBIGUOUS, log the original URL, target URL, method, and cache decision.
For telemetry, record HTTP 300, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.