2015-11-06 22:55:41 +01:00
|
|
|
---
|
|
|
|
|
set: 4
|
|
|
|
|
code: 421
|
|
|
|
|
title: Misdirected Request
|
2015-11-07 05:34:40 +01:00
|
|
|
references:
|
|
|
|
|
"Rails HTTP Status Symbol": ":misdirected_request"
|
2015-11-06 22:55:41 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-07 06:45:46 +01:00
|
|
|
The 421 Misdirected Request status code indicates that the request was
|
2015-11-07 05:34:40 +01:00
|
|
|
directed at a server that is not able to produce a response. This can be sent by
|
|
|
|
|
a server that is not configured to produce responses for the combination of
|
|
|
|
|
scheme and authority that are included in the request URI.
|
|
|
|
|
|
|
|
|
|
Clients receiving a 421 (Misdirected Request) response from a server MAY retry
|
|
|
|
|
the request -- whether the request method is idempotent or not -- over a
|
|
|
|
|
different connection. This is possible if a connection is reused
|
|
|
|
|
([RFC7540 Section 9.1.1][2]) or if an alternative service is selected
|
|
|
|
|
[ALT-SVC][3].
|
|
|
|
|
|
|
|
|
|
This status code MUST NOT be generated by proxies.
|
|
|
|
|
|
|
|
|
|
A 421 response is cacheable by default, i.e., unless otherwise indicated by the
|
|
|
|
|
method definition or explicit cache controls
|
|
|
|
|
(see [Section 4.2.2 of RFC7234][4]).
|
|
|
|
|
|
|
|
|
|
Source: [RFC7540 Section 9.1.2][1]
|
|
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7540#section-9.1.2>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7540#section-9.1.1>
|
|
|
|
|
[3]: <http://tools.ietf.org/html/rfc7540#ref-ALT-SVC>
|
|
|
|
|
[4]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|
