


How to solve the problem of not being able to upload files above 48MB when uploading video tiles using JS, PHP and Apache?
Apr 01, 2025 am 11:00 AMBreakthrough 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

Undress AI Tool
Undress images for free

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

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

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

Software preparation I am using a virtual machine with CentOS-6.6, with the host name repo. Refer to the steps to install a Linux virtual machine in Windows, I installed JDK in that virtual machine, refer to the guide to installing JDK in Linux. In addition, the virtual machine is configured with a key-free login itself, and the settings for configuring key-free login between each virtual machine are referenced. The download address of Hadoop installation package is: https://mirrors.aliyun.com/apache/hadoop/common/. I am using hadoop 2.6.5 version. Upload the Hadoop installation package to the server and unzip [root@repo~]#tarzxv

NGINX and Apache are both powerful web servers, each with unique advantages and disadvantages in terms of performance, scalability and efficiency. 1) NGINX performs well when handling static content and reverse proxying, suitable for high concurrency scenarios. 2) Apache performs better when processing dynamic content and is suitable for projects that require rich module support. The selection of a server should be decided based on project requirements and scenarios.

NGINX is more suitable for handling high concurrent connections, while Apache is more suitable for scenarios where complex configurations and module extensions are required. 1.NGINX is known for its high performance and low resource consumption, and is suitable for high concurrency. 2.Apache is known for its stability and rich module extensions, which are suitable for complex configuration needs.

NGINX and Apache each have their own advantages and disadvantages, and the choice should be based on specific needs. 1.NGINX is suitable for high concurrency scenarios because of its asynchronous non-blocking architecture. 2. Apache is suitable for low-concurrency scenarios that require complex configurations, because of its modular design.

The steps to deploy a Joomla website on PhpStudy include: 1) Configure PhpStudy, ensure that Apache and MySQL services run and check PHP version compatibility; 2) Download and decompress PhpStudy's website from the official Joomla website, and then complete the installation through the browser according to the installation wizard; 3) Make basic configurations, such as setting the website name and adding content.

PHP code can be executed in many ways: 1. Use the command line to directly enter the "php file name" to execute the script; 2. Put the file into the document root directory and access it through the browser through the web server; 3. Run it in the IDE and use the built-in debugging tool; 4. Use the online PHP sandbox or code execution platform for testing.

Updating the Tomcat version in the Debian system generally includes the following process: Before performing the update operation, be sure to do a complete backup of the existing Tomcat environment. This covers the /opt/tomcat folder and its related configuration documents, such as server.xml, context.xml, and web.xml. The backup task can be completed through the following command: sudocp-r/opt/tomcat/opt/tomcat_backup Get the new version Tomcat Go to ApacheTomcat's official website to download the latest version. According to your Debian system

Reasons for system performance not recovered after uninstalling the Apache service may include resource occupancy by other services, error messages in log files, resource consumption by abnormal processes, network connection problems, and file system residues. First, check whether there are other services or processes before uninstalling with Apache; second, pay attention to the operating system's log files and find error messages that may occur during the uninstallation process; second, check the system's memory usage and CPU load, and find out abnormal processes; then, use the netstat or ss command to view the network connection status to ensure that no ports are occupied by other services; finally, clean up the remaining configuration files and log files after uninstallation to avoid occupying disk space.
