417 Expectation Failed
4xx client error
The server cannot meet the expectation sent in the Expect header, most often an Expect: 100-continue the hop does not understand.
Common causes
- An intermediary strips or mishandles Expect: 100-continue.
- A custom Expect value is unsupported.
- An old server build lacks expect handling.
How to fix it
- Make the proxy forward Expect instead of answering it locally.
- Upgrade the server component that mishandles the header.
- Disable the Expect header for clients where it is optional.
What it means for redirects and SEO
Expectation failures usually come from intermediaries that strip 100-continue handling. Bots seldom send Expect. Fix it at the proxy rather than the app.