| Previous | Next |
| HTTP_E_STATUS_PRECOND_FAILED | HTTP_E_STATUS_URI_TOO_LONG |
HTTP_E_STATUS_REQUEST_TOO_LARGE
HTTP_E_STATUS_REQUEST_TOO_LARGE maps to HTTP 413 Content Too Large. The server refuses to process the request because the content is larger than the server is willing or able to handle.
What to check
- Measure the complete request body after encoding and multipart framing, not only the original file size.
- Compare application, reverse-proxy, gateway, and WAF request-size limits.
- If the limit is temporary, the response can include
Retry-After; otherwise use an explicitly supported chunking or upload workflow.
RFC 9110: 413 Content Too Large
Looking for a different code? Search another status or error code.