417
Expectation Failed
Client errors (4xx)·RFC 9110
What 417 means
The expectation in the Expect request header could not be met.
Typically returned when the server cannot satisfy an "Expect: 100-continue".
Client errors (4xx)
The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Other 4xx codes
400Bad Request401Unauthorized402Payment Required403Forbidden404Not Found405Method Not Allowed406Not Acceptable407Proxy Authentication Required408Request Timeout409Conflict410Gone411Length Required412Precondition Failed413Content Too Large414URI Too Long415Unsupported Media Type416Range Not Satisfiable418I'm a teapot421Misdirected Request422Unprocessable Content423Locked424Failed Dependency425Too Early426Upgrade Required428Precondition Required429Too Many Requests431Request Header Fields Too Large451Unavailable For Legal Reasons
FAQ — 417
What does HTTP 417 mean?
417 Expectation Failed: The expectation in the Expect request header could not be met. Typically returned when the server cannot satisfy an "Expect: 100-continue".
Which class does status code 417 belong to?
417 is a Client errors (4xx) code. The request contains an error from the client — bad syntax, missing auth or a wrong URL.
Where is the 417 code defined?
Status code 417 is defined in RFC 9110 and is part of the IANA HTTP Status Code Registry.