Code

405 Method Not Allowed (Method used not allowed)

Access methods (e.g., GET, POST, PUT) are not allowed for this resource.

Solution: Check and correct the access method.

406 Not Acceptable (Not Accepted)

The server cannot provide content that matches the Accept headers sent by the client.

Solution: Edit Accept Headers or modify content to match 405 Method Not Allowed (method used is not allowed)

Access methods (e.g., GET, POST, PUT) are not allowed for this resource.

Solution: Check and correct the access method.

406 Not Acceptable (Not Accepted)

The server cannot provide content that matches the Accept headers sent by the client.

Solution: Fix Accept headers or modify content to meet needs.

407 Proxy Authentication Required (Requires authentication via Proxy)

The identity must be confirmed with the proxy before accessing the resource.

Solution: Confirm the identity to the proxy as required.

408 Timeout Request (Timeout Request)

The server timed out, waiting for a request from the client.

Solution: Try again. Or check the network connection.

409 Conflict (Conflict)

The request cannot be processed because it conflicts with the current state of the resource.

Solution: Edit the data to not conflict with the current state.

410 Gone (gone)

The resource no longer exists and has no new address. It is different from 404 in that this information is permanently removed.

Solution: Remove the link pointing to this resource, as it no longer exists.

411 Length Required (Required Length)

The length of content must be specified in the request header.

Solution: Add Content-Length header to request

412 Precondition Failed (Precondition Failed)

The condition defined in the request header does not exist.

How to fix: Check and fix the conditions in the request header.

413 Too Large Payload (Too Large Payload)

The size of the request is too large for the server to accept.

Solution: Reduce the size of the transmitted data, or divide the transmission into subsections.

414 URI Too Long (URI Too Long)

The URI is too long for the server to accept.

Solution: Reduce the length of the URI or use the POST method instead of GET.

415 Unsupported Media Type (is unsupported media)

The server does not support the type of media the request sent.

Solution: Use the type of media the server supports.

416 Range Not Satisfiable

The range of data requested could not be responded to.

Solution: Monitor and modify the range of requested data.

417 Expectation Failed (Can't Do As Expected)

The server cannot meet the expectations specified in the Expect header.

Solution: Check and edit the Expect header in the request.

418 I'm a teapot (I'm a teapot)

The humor code stemmed from April Fools "1998 RFC that listed the device as a teapot and refused to brew coffee.

Solution: No need to fix it, as it is code used for entertainment rather than identifying real problems.

421 Misdirected Request (Misdirected Request)

The request was sent to a server that failed to generate a response. It may have been caused by an incorrect DNS or load balancer setting.

Solution: Check the DNS and server configuration that it is properly set.

422 Unprocessable Entity (Entity cannot be processed)

The request is grammatically correct, but there is a semantic error, making it impossible to process.

Solution: Verify the accuracy of the data sent to it, especially in parts of JSON or XML.

423 Locked (Locked)

The resource requesting access is locked. It is often found on WebDAV when editing files simultaneously.

Solution: Wait for the resource to be unlocked, or contact the person who is using it.

424 Failed Dependency (Dependency Failure)

The request failed because the previous request failed. It is often found in working as a dependent set.

Solution: Fix the previous request first and then try again.

425 Too Early (still too early)

The server is unwilling to process requests that may be resent. Used to prevent replay attacks.

Solution: Wait a minute and try sending the request again. Or check that the system has attack protection.

426 Upgrade Required (Upgrade Required)

The client needs to upgrade the protocol or version to have access to the resource.

Solution: Upgrade the protocol or software as specified in the response header.

428 Preconditional Required (with necessary preconditions)

The server wants the request to have a precondition. It is often used to prevent "lost update" problems in multi-user environments.

Solution: Add an If-Match header or necessary condition to the request.

429 Too Many Requests (Too Many Requests)