HTTP 413 Content Too Large
The request body is bigger than the server accepts.
Common causes and fixes
- Raise the body limit (for example client_max_body_size in nginx) or upload in chunks.
Example response
HTTP
HTTP/1.1 413 Content Too Large
Content-Type: application/json; charset=utf-8
{ "error": "Content Too Large" }Look up the headers shown here in the HTTP headers reference.
Common questions
- What does HTTP 413 mean?
- Content Too Large. The request body is bigger than the server accepts.
- How do I fix a 413 error?
- Raise the body limit (for example client_max_body_size in nginx) or upload in chunks.
- Is 413 an error?
- Yes. 4xx codes are client errors: The request contains a mistake or can't be fulfilled as sent.
Other 4xx codes
400 Bad Request401 Unauthorized402 Payment Required403 Forbidden404 Not Found405 Method Not Allowed406 Not Acceptable407 Proxy Authentication Required408 Request Timeout409 Conflict410 Gone411 Length Required412 Precondition Failed414 URI Too Long415 Unsupported Media Type416 Range Not Satisfiable417 Expectation Failed418 I'm a teapot421 Misdirected Request422 Unprocessable Content423 Locked424 Failed Dependency425 Too Early426 Upgrade Required428 Precondition Required429 Too Many Requests431 Request Header Fields Too Large451 Unavailable For Legal Reasons