


How to solve the problem of not being able to upload files above 48MB when uploading video tiles using JS, PHP and Apache?
Breakthrough 48MB limit: JS, PHP and Apache video slicing upload solutions
In small project development, handling large file uploads often encounter challenges. This article will share a practical case: how to overcome the 48MB file size limit when uploading video slicing using JavaScript, PHP and Apache.
Problem: 48MB upload bottleneck
The project adopts a slice upload scheme, which theoretically supports 2GB files, 1MB per slice, and up to 2,000 pieces. However, in actual tests, after uploading more than 48MB (about 48 pieces), subsequent requests return 500 errors. Even if the slice size is resized to 10MB, the problem persists.
Code analysis and improvement
JavaScript code:
In the original code, FormData
object was initialized only once, resulting in each request carrying all uploaded slice data, which ultimately exceeded Apache's fcgidmaxrequestlen
limit.
The improved JavaScript code is as follows. The key is to re-instrate FormData
object before each request is sent:
function videoFileUpload() { const LENGTH = 1024 * 1024; // 1MB let start = 0; let end = start LENGTH; let blob_num = 1; let is_stop = 0; this.start = function () { const file = files.files[0]; const blob = cutFile(file); sendFile(blob, file); blob_num ; } // ... (The rest of the code remains the same) ... function sendFile(blob, file) { if (is_stop === 0) { const xhr = new XMLHttpRequest(); const form_data = new FormData(); // Key: Reinstand FormData every time const total_blob_num = Math.ceil(file.size / LENGTH); form_data.append('file', blob); form_data.append('blob_num', blob_num); form_data.append('total_blob_num', total_blob_num); form_data.append('file_name', file.name); xhr.open('POST', '/upload.php', false); // ... (The rest of the code remains the same) ... } } // ... (The rest of the code remains the same) ... }
PHP code:
File merging logic in PHP code may also have memory efficiency issues. For oversized files, streaming is recommended to avoid reading all slices into memory at once. (The PHP code is omitted here because the original code does not provide obvious memory leaks or efficiency issues, and the focus of improvement is on the JS side)
Solution Summary
The core of the problem lies in the reuse of FormData
objects in JavaScript code. By reinstaging the FormData
object before each request, data accumulation is avoided, thus solving the 48MB upload limit. For the PHP side, if memory problems occur when processing large files, you need to further optimize the file merging logic and adopt streaming processing. This improvement solution effectively solves the problem of large file uploads and ensures the stability and reliability of video slicing uploads.
The above is the detailed content of How to solve the problem of not being able to upload files above 48MB when uploading video tiles using JS, PHP and Apache?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

To set up a CGI directory in Apache, you need to perform the following steps: Create a CGI directory such as "cgi-bin", and grant Apache write permissions. Add the "ScriptAlias" directive block in the Apache configuration file to map the CGI directory to the "/cgi-bin" URL. Restart Apache.

When the Apache 80 port is occupied, the solution is as follows: find out the process that occupies the port and close it. Check the firewall settings to make sure Apache is not blocked. If the above method does not work, please reconfigure Apache to use a different port. Restart the Apache service.

Apache connects to a database requires the following steps: Install the database driver. Configure the web.xml file to create a connection pool. Create a JDBC data source and specify the connection settings. Use the JDBC API to access the database from Java code, including getting connections, creating statements, binding parameters, executing queries or updates, and processing results.

There are 3 ways to view the version on the Apache server: via the command line (apachectl -v or apache2ctl -v), check the server status page (http://<server IP or domain name>/server-status), or view the Apache configuration file (ServerVersion: Apache/<version number>).

How to view the Apache version? Start the Apache server: Use sudo service apache2 start to start the server. View version number: Use one of the following methods to view version: Command line: Run the apache2 -v command. Server Status Page: Access the default port of the Apache server (usually 80) in a web browser, and the version information is displayed at the bottom of the page.

How to configure Zend in Apache? The steps to configure Zend Framework in an Apache Web Server are as follows: Install Zend Framework and extract it into the Web Server directory. Create a .htaccess file. Create the Zend application directory and add the index.php file. Configure the Zend application (application.ini). Restart the Apache Web server.

To delete an extra ServerName directive from Apache, you can take the following steps: Identify and delete the extra ServerName directive. Restart Apache to make the changes take effect. Check the configuration file to verify changes. Test the server to make sure the problem is resolved.

Apache cannot start because the following reasons may be: Configuration file syntax error. Conflict with other application ports. Permissions issue. Out of memory. Process deadlock. Daemon failure. SELinux permissions issues. Firewall problem. Software conflict.
