tool::http-status-detail
413 Content Too Large
The request body exceeds the server's size limit.
Status Code
413
Name
Content Too Large
Category
4xxDetailed Explanation
HTTP 413 Content Too Large (formerly Request Entity Too Large) indicates the request body exceeds the maximum size the server will accept. It occurs with large file uploads, oversized JSON payloads, or when server-configured size limits are exceeded. The server may abort processing and close the connection.
Common Causes
- ▸A file upload exceeds the server's upload size limit
- ▸The API request body exceeds the server's maximum payload limit
- ▸The Nginx client_max_body_size setting is exceeded
- ▸A cloud function request size limit is exceeded (e.g., AWS Lambda: 6MB)
How to Fix
- 1.Increase the Nginx client_max_body_size setting (e.g., client_max_body_size 50M)
- 2.For large files, use chunked uploads or Pre-signed URLs
- 3.Reduce the JSON payload size or implement pagination
- 4.If a Retry-After header is present, wait before retrying
Related HTTP Headers
Content-LengthRetry-AfterResponse Example
HTTP/1.1 413 Content Too Large
Content-Type: application/json
{"error":"payload_too_large","message":"Request body exceeds 10MB limit","maxSize":"10MB"}Related Status Codes
400Bad RequestThe server could not understand the request due to invalid syntax.→401UnauthorizedAuthentication is required and has failed or not been provided.→402Payment RequiredReserved for future use; some services use it for payment walls.→403ForbiddenThe server refuses to fulfill the request (authenticated but unauthorized).→404Not FoundThe requested resource could not be found.→
ad · 300×250
// related tools