- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 417 Expectation Failed
417 Expectation Failed
The server can't meet what the Expect header of the request asks. In practice that is always Expect: 100-continue.
- Class
- 4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
- Defined in
- RFC 9110
What causes it
A client sends Expect: 100-continue to ask whether it may send a large body, and a server or a proxy on the way doesn't support that mechanism and says so with a 417.
What to do about it
Send the request again without the Expect header: nothing else about it was wrong. With curl that is -H "Expect:", and most HTTP libraries have a setting for it. If your own proxy is the one that answers 417, it is old or strictly configured.
Not to be confused with
| 100 Continue | The answer the client was hoping for. |
|---|---|
| 413 Content Too Large | The server understood the question and finds the body too large. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.
Other 4xx codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 423 Locked
- 424 Failed Dependency
- 425 Too Early
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons