---
id: 3151ee2f-a529-4f69-b2a1-c4ff7a1dd0c6
---

# Apache File Upload Size Limit Exceeded Incident
---

This incident type pertains to a situation where the Apache file that is being uploaded exceeds the size limit that is set for the upload. Such a scenario occurs when the file's size is larger than what the server is configured to handle. This incident can result in the file upload process being halted, which can cause delays in the system's functioning.

### Parameters
```shell
export APACHE_CONFIG_FILE="PLACEHOLDER"

export APACHE_ERROR_LOG="PLACEHOLDER"

export FILE_PATH="PLACEHOLDER"

export NEW_FILE_SIZE_LIMIT="PLACEHOLDER"

export PATH_TO_PHP_INI_FILE="PLACEHOLDER"
```

## Debug

### Check the Apache version
```shell
httpd -v
```

### Check the Apache configuration file for the max file upload size limit set
```shell
grep -i "LimitRequestBody" ${APACHE_CONFIG_FILE}
```

### Check the Apache error log for any error messages related to file upload
```shell
tail -f ${APACHE_ERROR_LOG}
```

### Check the file size of the file being uploaded
```shell
ls -lh ${FILE_PATH}
```

### Check the available space on the server where Apache is running
```shell
df -h
```

### Restart the Apache service to apply any changes made to the configuration file
```shell
systemctl restart httpd
```

### Check the status of the Apache service
```shell
systemctl status httpd
```

## Repair

### Increase the upload file size limit in the Apache server configuration file. This can be achieved by modifying the "upload_max_filesize" and "post_max_size" fields in the "php.ini" file.
```shell


#!/bin/bash



# Set the new file size limit

NEW_SIZE_LIMIT=${NEW_FILE_SIZE_LIMIT}



# Set the path to the php.ini file

PHP_INI_PATH=${PATH_TO_PHP_INI_FILE}



# Update the "upload_max_filesize" field in the php.ini file

sed -i "s/upload_max_filesize = .*/upload_max_filesize = ${NEW_SIZE_LIMIT}/" ${PHP_INI_PATH}



# Update the "post_max_size" field in the php.ini file

sed -i "s/post_max_size = .*/post_max_size = ${NEW_SIZE_LIMIT}/" ${PHP_INI_PATH}



# Restart Apache to apply the changes

service apache2 restart



echo "Upload file size limit updated to ${NEW_SIZE_LIMIT}"


```

This incident type pertains to a situation where the Apache file that is being uploaded exceeds the size limit that is set for the upload. Such a scenario occurs when the file's size is larger than what the server is configured to handle. This incident can result in the file upload process being halted, which can cause delays in the system's functioning.


This incident type occurs when the size of HTTP request headers or payload exceeds the limits set by Tomcat server. When this happens, the server may reject the request or return an error message, causing disruption to the normal functioning of the web application. This can be caused by a variety of factors, including large file uploads, excessive use of cookies or query parameters, or attacks that intentionally send oversized requests.


Tomcat HTTP Request Headers or Payload Size Exceeds Limits.

This incident type refers to frequent mismatches between the virtual hosts configured on an Apache server. This can cause issues with routing traffic to the intended web application or website, resulting in downtime or other problems. It is important to address these mismatches promptly to ensure the proper functioning of the server and any associated applications.


Virtual Host Mismatches on Apache Server.

This incident type refers to an unauthorized access to directories in Apache HTTPD, which is a widely used web server software. It means that someone was able to access files or directories that they were not supposed to, without having proper authorization. This type of incident can potentially lead to sensitive data being exposed or even stolen, and can compromise the security of the server and the applications running on it.


Unauthorized Directory Access in Apache HTTPD.

This incident type refers to a security vulnerability in the SSL/TLS configuration of the Apache HTTP Server, which can leave the server and its users vulnerable to attacks. The SSL/TLS configuration is responsible for encrypting the communication between the server and its clients, and if it is not configured properly, it can be exploited by hackers to intercept or modify sensitive data. This type of incident requires immediate attention from software engineers to ensure that the SSL/TLS configuration is properly configured to prevent any potential security threats.


Inadequate SSL/TLS Configuration for Apache HTTP Server.

This incident type refers to a situation where the number of child processes created by an Apache server reaches a high threshold, causing performance issues and potentially leading to server crashes. This can occur due to factors such as high traffic volume or misconfigured server settings. The incident requires investigation and mitigation to restore normal server functioning and prevent future occurrences.


High Number of Apache Child Processes Incident

```shell
export APACHE_CONFIG_FILE="PLACEHOLDER"

export APACHE_ERROR_LOG="PLACEHOLDER"

export FILE_PATH="PLACEHOLDER"

export NEW_FILE_SIZE_LIMIT="PLACEHOLDER"

export PATH_TO_PHP_INI_FILE="PLACEHOLDER"
```


### Check the Apache version

```shell
httpd -v
```

### Check the Apache configuration file for the max file upload size limit set

```shell
grep -i "LimitRequestBody" ${APACHE_CONFIG_FILE}
```

### Check the Apache error log for any error messages related to file upload

```shell
tail -f ${APACHE_ERROR_LOG}
```

### Check the file size of the file being uploaded

```shell
ls -lh ${FILE_PATH}
```

### Check the available space on the server where Apache is running

```shell
df -h
```

### Restart the Apache service to apply any changes made to the configuration file

```shell
systemctl restart httpd
```

### Check the status of the Apache service

```shell
systemctl status httpd
```


### Increase the upload file size limit in the Apache server configuration file. This can be achieved by modifying the "upload\_max\_filesize" and "post\_max\_size" fields in the "php.ini" file.

```shell


#!/bin/bash



# Set the new file size limit

NEW_SIZE_LIMIT=${NEW_FILE_SIZE_LIMIT}



# Set the path to the php.ini file

PHP_INI_PATH=${PATH_TO_PHP_INI_FILE}



# Update the "upload_max_filesize" field in the php.ini file

sed -i "s/upload_max_filesize = .*/upload_max_filesize = ${NEW_SIZE_LIMIT}/" ${PHP_INI_PATH}



# Update the "post_max_size" field in the php.ini file

sed -i "s/post_max_size = .*/post_max_size = ${NEW_SIZE_LIMIT}/" ${PHP_INI_PATH}



# Restart Apache to apply the changes

service apache2 restart



echo "Upload file size limit updated to ${NEW_SIZE_LIMIT}"


```


Apache File Upload Size Limit Exceeded Incident

Overview

Parameters

Debug

Check the Apache version

Check the Apache configuration file for the max file upload size limit set

Check the file size of the file being uploaded

Check the available space on the server where Apache is running

Restart the Apache service to apply any changes made to the configuration file

Check the status of the Apache service

Repair

Increase the upload file size limit in the Apache server configuration file. This can be achieved by modifying the "upload_max_filesize" and "post_max_size" fields in the "php.ini" file.

Learn more

Related Runbooks

Tomcat HTTP Request Headers or Payload Size Exceeds Limits.

Virtual Host Mismatches on Apache Server.

Unauthorized Directory Access in Apache HTTPD.

Inadequate SSL/TLS Configuration for Apache HTTP Server.

Support