Skip to the content

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

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

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 ContinueThe answer the client was hoping for.
413 Content Too LargeThe 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.

See all 12