cPanel & WHM no longer develops EasyApache 3 and only releases security updates for it. We will deprecate EasyApache 3 on December 31, 2018. After that date, we will no longer update EasyApache 3. In cPanel & WHM version 78, we will remove support for EasyApache 3. For more information, read our cPanel Long-Term Support documentation. If you do not upgrade to EasyApache 4, you cannot upgrade to cPanel & WHM version 78. We strongly recommend that you upgrade to EasyApache 4. For more information, read our EasyApache 4 documentation.
Apache Module: Expires - EasyApache - cPanel Documentation
Page tree
Skip to end of metadata
Go to start of metadata

Overview

The mod_expires Apache module adds functionality to Apache that allows you to define the length time before a client will consider data out of date.

This module allows you to define one or both of the following values:

  • The max-age field of the Cache-Control header.
  • The Expires header.

Usage

Use this module if you wish to define when a web browser or server will consider your server's data out of date. After you install the module, you must define the max-age value or the Expires header in either .htaccess files or in your Apache configuration files.

For more information how to customize your Apache configuration, read our Advanced Apache Configuration documentation.


Featured documentation

  EasyApache 3

IntroductionFAQ

Change Log Release Notes  

ProfilesCustomization

Tomcat

Migrate from Tomcat 5.5 to 7

How to Deploy Java Applications


Important:

EasyApache 3 does not support new installations of Tomcat.

As of cPanel & WHM version 76, EasyApache 4 now supports Tomcat 8.5. For more information, read our Tomcat documentation.

Requirements

This module has no requirements.

Compatibility

This module has no known compatibility issues.

How to install or uninstall mod_expires

Module status in default profiles

The following EasyApache profiles include the mod_expires Apache module by default:

  • Basic
  • Mod Ruid2
  • MPM ITK

Note:

The Mod Ruid2 profile is only available if you do not use CloudLinux.

Installation steps

If you do not select one of the default EasyApache profiles, perform the following steps to install or uninstall the mod_expires Apache module:

  1. Run EasyApache in WHM's EasyApache 3 interface (Home >> Software >> EasyApache 3).

    Notes:

    • To access EasyApache from the command line interface, run the /scripts/easyapache script as the root user.
    • For more information on EasyApache, read our EasyApache documentation.
  2. Select the profile that you wish to modify.

  3. Click the  that corresponds to your selection.

  4. Click Next Step in the Apache Version stage.
  5. Click Next Step in the PHP Version stage.
  6. Click Exhaustive Options List in the Short Options List stage.
  7. Perform one of the following actions in the Exhaustive Options List stage:
    • To install the mod_expires Apache module, select the Expires option.
    • To uninstall the mod_expires Apache module, deselect the Expires option.
  8. Click Save and Build.

How to enable or disable the module in a custom EasyApache profile file

The following table provides information about how EasyApache refers to the mod_expires Apache module: 

EasyApache module namemod_expires
EasyApache Profile EntryApache::optmods::Expires

To enable or disable the mod_expires Apache module in a custom EasyApache profile file, set the Apache:optmods:Expires profile entry to one of the following values:

  • 1 – This value enables the module.
  • 0 – This value disables the module.

History

The following table provides information on changes to the mod_expires Apache module within EasyApache, and content changes to this document:

Date
EasyApache version
Action
Details
2/11/20143.24.11Doc updateImplemented case 73225: Remove Apache 1.3 and 2.0
1/31/20133.18.0Doc updateImplemented case 51105: Update for Apache 2.4

Vendor documentation

The following text is an excerpt from Apache's website:

This module controls the setting of the Expires HTTP header and the max-age directive of the Cache-Control HTTP header in server responses. The expiration date can set to be relative to either the time the source file was last modified, or to the time of the client access.

For more information on the mod_expires Apache module, click the following links: