HTTP Status Codes

HTTP 204 No Content

By Admin in 2xx Success Error Code, HTTP Status Codes

HTTP 204 No Content | HTTP 204 Error Code: The HTTP 204 Status Code means that the server has successfully processed the client request but doesn’t have any additional content to return the user. The metadata refers to the target resource and its representation after the requested action was implemented. For instance, if a 204 HTTP status code is received in response to a PUT request and the response contains an ETag header field, then the PUT was successful, and the ETag field-value contains the entity-tag for the new representation of that target resource.

HTTP 204 No Content

HTTP 204 No Content

The user need not change away from its present document view, as the 204 response code allows the server to indicate the action has been performed to the target resource. The server believes that the user agent will acknowledge the success to its users and apply any new metadata to its active representation. Usually, a 204 No Content code is used in document editing relating to a “save” action, meaning that the particular document is saved and remains active for editing.

The HTTP 204 No Content is terminated by the first blank line after the header fields as it cannot contain a message body.

204 No Content Code References

The code references of HTTP 204 No Content is listed below,

  • Rails HTTP Status Symbol :no_content
  • Go HTTP Status Constant http.StatusNoContent
  • Symfony HTTP Status Constant Response::HTTP_NO_CONTENT
  • Python2 HTTP Status Constant httplib.NO_CONTENT
  • Python3+ HTTP Status Constant http.client.NO_CONTENT
  • Python3.5+ HTTP Status Constant http.HTTPStatus.NO_CONTENT

Know more about HTTP Error Codes from HTTP Status Codes.

Other HTTP Status Codes

HTTP Verbs

HTTP Methods

1xx Informational

100 Continue

101 Switching Protocol

102 Processing

2xx Success

200 OK

201 Created

202 Accepted

203 Non-Authoritative Information

204 No Content

205 Reset Content

206 Partial Content

207 Multi-Status (WebDAV; RFC 4918)

208 Already Reported (WebDAV; RFC 5842)

226 IM Used (RFC 3229)

3xx Redirection

300 Multiple Choice

301 Moved Permanently

302 Found

303 See Other

304 Not Modified

305 Use Proxy

306 Unused

307 Temporary Redirect

308 Temporary Redirect

4xx Client Error

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

411 Length Required

412 Precondition Failed

413 Payload Too Large

414 URI Too Long

415 Unsupported Media Type

416 Requested Range Not Satisfiable

417 Expectation Failed

418 I’m a teapot (RFC 2324)

421 Misdirected Request

422 Unprocessable Entity (WebDAV; RFC 4918)

423 Locked (WebDAV; RFC 4918)

424 Failed Dependency (WebDAV; RFC 4918)

426 Upgrade Required

428 Precondition Required

429 Too Many Requests

431 Request Header Fields Too Large

451 Unavailable For Legal Reasons

5xx Server Error

500 Internal Server Error

502 Bad Gateway

503 Service Unavailable

504 Gateway Timeout

505 HTTP Version Not Supported

506 Variant Also Negotiates

507 Variant Also Negotiates

508 Loop Detected (WebDAV; RFC 5842)

510 Not Extended (RFC 2774)

511 Network Authentication Required

Unofficial Error Code List

103 Checkpoint

420 Method Failure (Spring Framework)

420 Enhance Your Calm (Twitter)

450 Blocked by Windows Parental Controls (Microsoft)

498 Invalid Token (Esri)

499 Token Required (Esri)

499 Request forbidden by antivirus

509 Bandwidth Limit Exceeded (Apache Web Server/cPanel)

530 Site is frozen

Internet Information Services Error Code List

449 Retry With

451 Redirect

444 No Response

Nginx Error Code List

495 SSL Certificate Error

496 SSL Certificate Required

497 HTTP Request Sent to HTTPS Port

499 Client Closed Request

CloudFlare Error Code List

520 Unknown Error

521 Web Server Is Down

522 Connection Timed Out

523 Origin Is Unreachable

524 A Timeout Occurred

525 SSL Handshake Failed

526 Invalid SSL Certificate

Post a Reply

Your email address will not be published. Required fields are marked *