


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

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.

The command to start the Apache service on macOS is sudoapachectlstart, and the configuration file is located in /etc/apache2/. The main steps include: 1. Edit the httpd.conf file, modify the Listen port such as Listen8080; 2. Adjust the DocumentRoot path to the personal directory such as /Users/your_username/Sites, and update the corresponding permission settings; 3. Use the sudoapachectlgraceful command to restart Apache to ensure that the configuration takes effect; 4. Enable the mod_deflate module to compress data to improve page loading speed.

The reasons for file deletion failure during Apache uninstall include file permission issues, locking files, and running processes. Solutions include: 1. Stop the Apache service: sudosystemctlstoppapache2; 2. Manually delete the Apache directory: sudorm-rf/etc/apache2/usr/sbin/apache2; 3. Use lsof to find and terminate the process of locking the file: sudolsof|grepapache2, and then sudokill-9; 4. Try to delete the file again.

Configuring Apache to connect to MySQL database requires the following steps: 1. Make sure that Apache and MySQL are installed; 2. Configuring Apache to support PHP, by adding LoadModule and AddHandler instructions in httpd.conf or apache2.conf; 3. Configuring PHP to connect to MySQL, enable mysqli extension in php.ini; 4. Create and test the connected PHP file. Through these steps, the connection between Apache and MySQL can be successfully implemented.

There are many methods and tools for monitoring Hadoop clusters on Debian systems. The following are some commonly used monitoring tools and their usage methods: Hadoop's own monitoring tool HadoopAdminUI: Access the HadoopAdminUI interface through a browser to intuitively understand the cluster status and resource utilization. HadoopResourceManager: Access the ResourceManager WebUI (usually http://ResourceManager-IP:8088) to monitor cluster resource usage and job status. Hadoop
