What does HTTP status 413 (Request Too Large) mean?

 
Could be also:
ConstantTypeOS
ERROR_RWRAW_ENCRYPTED_INVALID_EDATAINFO_PARAMETERWin32 errorWindows
CLUSTER_SVHDX_LIVEDUMPBugCheck CodeWindows
Previous Next
HTTP_STATUS_PRECOND_FAILED HTTP_STATUS_URI_TOO_LONG

HTTP_STATUS_REQUEST_TOO_LARGE

The limit can be enforced by the origin, reverse proxy, API gateway, or application framework. The response may include Retry-After when the condition is temporary, but many limits are configuration policies.

Measure the encoded byte size, including multipart overhead. Reduce the payload, split uploads, or change the documented server-side limit rather than retrying the unchanged request.

The server may reject the request immediately or after reading enough data to determine that its size limit is exceeded. Check both proxy and application limits, because either layer can generate the response. Splitting, compressing, or uploading through a different endpoint is valid only when the application protocol supports it.

RFC 9110: HTTP Semantics


Looking for a different code? Search another status or error code.