- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 411 Length Required
411 Length Required
The server refuses the request because it has a body and no Content-Length header that says how long the body is.
- Class
- 4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
- Defined in
- RFC 9110
What causes it
When a request with a body arrives without Content-Length and the server won't take a body of unknown size. That mostly happens when the client sends the body in chunks, with Transfer-Encoding: chunked, to a server or proxy that doesn't accept that.
What to do about it
Send the length. Most HTTP libraries add Content-Length themselves when they know the size in advance, so hand them the body as a string or a buffer and not as a stream. A POST or PUT with an empty body may need an explicit Content-Length: 0.
Not to be confused with
| 413 Content Too Large | The length is known, and it is too much. |
|---|---|
| 400 Bad Request | Something else in the request is malformed. |
All codes are on the list of HTTP status codes, which can be searched by number and by word.
Other 4xx codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 423 Locked
- 424 Failed Dependency
- 425 Too Early
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons