4×× Client Error
421 Misdirected Request
The request was 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 reused1or if an alternative service is selected ALT-SVC.
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 controls2.
1 Connection Reuse RFC7540 Section 9.1.1
2 Calculating Heuristic Freshness RFC7234 Section 4.2.2
Source: RFC7540 Section 9.1.2
421 Code References
Rails HTTP Status Symbol :misdirected_request
421 Misdirected Request
The request was 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 reused1or if an alternative service is selected ALT-SVC.
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 controls2.
1 Connection Reuse RFC7540 Section 9.1.1
2 Calculating Heuristic Freshness RFC7234 Section 4.2.2
Source: RFC7540 Section 9.1.2
421 Code References
Rails HTTP Status Symbol :misdirected_request
No comments:
Post a Comment