100 Continue
1xx informational
Server received the request headers and the client should send the body, used with Expect: 100-continue to avoid uploading data the server would reject.
Common causes
- The client sent an Expect: 100-continue header before uploading a large body.
- A proxy or load balancer waits for the origin to approve the upload first.
- The application validates headers before it is willing to accept the payload.
How to fix it
- Respond with 100 promptly once headers pass validation, or send a final error if they fail.
- Disable Expect handling for small bodies where the round trip costs more than the upload.
- Raise client and proxy timeouts so a slow body send does not abort after the interim response.
What it means for redirects and SEO
Interim, so crawlers and link checkers never treat it as a final response. A client that stalls instead of sending the body wastes a crawl slot and shows up as a timeout in logs. Broken 100 handling rarely affects indexable pages directly.