[Fixed!] 413 Request Entity Too Large on WordPress, Chrome, Edge - MiniTool

HTTP 413 Error: Request Entity Too Large - Solution Guide

Encountering the "413 Request Entity is too large" error? This article will provide you with multiple solutions to this problem, for platforms such as WordPress, Google Chrome, and Microsoft Edge.

What is the "413 Request Entity Too Large" error?

"413 Request Entity Too Large" (also known as HTTP Error 413 or 413 Payload Too Large) is an error that occurs when the client sends a request volume to the server exceeds the server's processing capacity. 413 is one of the 4xx error codes, indicating that there is a problem between the browser and the server. "Requesting entity" refers to the information load requested by the client from the server.

Cause of error:

This error is usually accompanied by the message "Your client is making too large requests". There are two main reasons: the request body is not preloaded during the handshake process; or the size of the client request exceeds the size limit of the server file.

Workaround in WordPress:

Method 1: Upload smaller files

For images, you can use tools such as TinyJPG or IMG3Go to compress the file size. For plugins or themes, try looking for smaller alternatives.

Method 2: Upload large files through SFTP

Bypass the front-end interface and upload large files to the server directly through SFTP. Log in to your website and upload files to the server directory via SFTP.

Method 3: Modify PHP.ini file

PHP.ini File Management File Timeout, File Upload Size, and Resource Limits.

1. Open your hosting account, go to cPanel and find the PHP.ini file.
2. Right-click on the PHP.ini file and select "Edit". You will see the following code:
   • max_execution_time (maximum upload time)
   • upload_max_filesize (maximum upload file size)
   • post_max_size (maximum POST data size)
3. Modify the values ​​of these values ​​to the appropriate values ​​and save the changes.

Workaround in Chrome/Edge:

The following is a similar step for Microsoft Edge, taking Google Chrome as an example.

Method 1: Clear browser data

Clearing browser data is effective for many users.

1. Launch Chrome, click the three-dot icon, and select More Tools > Clear Browse Data.
2. Select the time range and check the browsing data to be cleared.

3. Click "Clear Data".

Method 2: Reset Chrome to factory default settings

This method resets your startup page, new tab page, search engine, and fixed tags, while deleting temporary data, but keeps data such as bookmarks, history and saved passwords.

1. Launch Chrome, click the three-dot icon, and select "Settings".
2. Go to Reset and Clean > Restore Settings to Its Original Default Value.

Follow the on-screen instructions.

Method 3: Reset the network adapter

The last method is to reset the network adapter.

1. Enter cmd in the search bar, find "Command Prompt", and right-click to select "Run as administrator".
2. Enter netsh Winsock reset in the command window and press Enter.

Through the above method, you should be able to resolve the "413 Request Entity is too large" error and upload the file successfully. Please try different solutions according to your specific situation.

The above is the detailed content of [Fixed!] 413 Request Entity Too Large on WordPress, Chrome, Edge - MiniTool. For more information, please follow other related articles on the PHP Chinese website!