litespeed / module-litemage

litespeed/module-litemage

LiteMage Full Page Cache for LiteSpeed Web Server

magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Fail Tests: N/A Security: Pass OSL-3.0, AFL-3.0

Are you the maintainer of litespeed?

Packagento pulls litespeed's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

magento2-LiteSpeed_LiteMage

Description

The LiteMage Cache module provides an improved caching solution alternative to the PageCache module and Varnish Cache. The module will replace the Varnish option to the cache selector in the administrator interface for easy switching.

For most use cases, LiteMage Cache can improve your stores' performance right out of the box. LiteMage Cache also reduces the complexity of your stack; only the LiteMage Extension and LiteSpeed Web Server are required*. There is no need for an NGINX reverse proxy nor a Varnish Cache instance because the server can handle HTTPS and HTTP/2 requests and cache the pages all in one application.

LiteMage Cache operates by taking information from Magento and instructing the LiteSpeed server on how to cache the page. Once the server knows how to cache it, future requests to the same page will be served directly from the server. Requests will never hit the Magento backend until a change occurs.

* For clustered setups, LiteSpeed Load Balancer is needed.

Prerequisites

LiteSpeed Web Server Enterprise Edition with Magento 2 set up and working.

Installation

The following steps assume that the Prerequisites mentioned above are met.

  1. Access a terminal as the Magento directory owner (e.g. "user1") and cd to the Magento 2 root directory. If logged in as root, do su user1 first.

  2. Set the store to developer mode:

    php bin/magento deploy:mode:set developer
    
  3. Download the zip package file from this repository.

  4. Unzip the source package. The unzipped directory should be named magento2-LiteSpeed_LiteMage-master.

  5. In the Magento 2 root directory, run the following command to create the needed directories:

    mkdir -p app/code/Litespeed/Litemage
    
  6. Move the contents from the GitHub directory to the newly created directory:

    mv /path/to/magento2-LiteSpeed_LiteMage-master/* app/code/Litespeed/Litemage/
    
  7. Confirm that the contents' owner is consistent with the other magento store files.

  8. Enable LiteMage 2 in magento:

    php bin/magento module:enable Litespeed_Litemage
    
  9. Upgrade the Magento setup:

    php bin/magento setup:upgrade
    
  10. Recompile code

    php bin/magento setup:di:compile
    
  11. If desired, switch back to production mode. The previous step may need to be repeated after the mode switch.

Enable LiteMage after installation:

  1. In the Magento 2 root directory's .htaccess file, add the following lines:

    <IfModule LiteSpeed>
    LiteMage on
    </IfModule>
    
  2. Log into the Magento admin page.

  3. In Store -> Configuration -> Advanced -> System, make sure LiteMage is enabled and the Full Page Cache setting has LiteMage selected.

  4. In System -> Cache Management, refresh configurations and page cache.

  5. Visit and refresh a page that should be cache enabled. Look for the LiteMage related response headers.

    Example:

    X-LiteSpeed-Cache: litemage,hit
    

Configuration

No further changes to your Magento 2 configurations should be necessary as LiteMage honors the same cacheable settings as varnish in the layout xml files.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
2.2.6 stable Fail Magento 2.4.7-2.4.9 Details 2026-05-29 20:12:11
2.2.5 stable Not tested Not yet tested Details 2025-05-14 17:58:33
2.2.4 stable Not tested Not yet tested Details 2024-03-20 19:15:27
2.2.3 stable Not tested Not yet tested Details 2024-02-14 14:49:07
2.2.2 stable Not tested Not yet tested Details 2023-09-28 19:24:09
2.2.1 stable Not tested Not yet tested Details 2023-07-27 20:09:05
2.2 stable Not tested Not yet tested Details 2023-07-19 21:00:25
2.1.9 stable Not tested Not yet tested Details 2022-05-18 04:59:20
2.1.7 stable Not tested Not yet tested Details 2020-08-07 03:47:48
2.1.6 stable Not tested Not yet tested Details 2020-06-18 03:23:43
2.1.5 stable Not tested Not yet tested Details 2019-11-05 20:44:54
2.1.4 stable Not tested Not yet tested Details 2019-10-28 14:08:49
2.1.3 stable Not tested Not yet tested Details 2019-07-26 23:19:10
2.1.2 stable Not tested Not yet tested Details 2019-07-01 15:55:45
2.1.1 stable Not tested Not yet tested Details 2019-06-21 22:26:35
2.1.0 stable Not tested Not yet tested Details 2019-02-11 22:16:02
2.0.10 stable Not tested Not yet tested Details 2018-11-19 21:44:20
2.0.9 stable Not tested Not yet tested Details 2018-11-02 19:07:08
2.0.8 stable Not tested Not yet tested Details 2017-12-15 20:22:33
2.0.7 stable Not tested Not yet tested Details 2017-11-09 21:41:32
2.0.6 stable Not tested Not yet tested Details 2017-10-25 18:33:31
2.0.5 stable Not tested Not yet tested Details 2017-02-12 02:01:05
2.0.4 stable Not tested Not yet tested Details 2017-01-23 00:16:00
2.0.3 stable Not tested Not yet tested Details 2017-01-09 21:40:43
2.0.2 stable Not tested Not yet tested Details 2017-01-03 06:04:18
2.0.1 stable Not tested Not yet tested Details 2016-11-11 21:52:07

Requires 5

Package Constraint
php >=7.4.0
ext-curl *
magento/module-page-cache *
magento/module-inventory-sales-api *
magento/framework *

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Pass
2.4.9 Pass Pass

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Fail 1481 5 errors, 1476 warnings (ruleset: Magento2) — 1386 auto-fixable with phpcbf
PHPMD Warning 41 41 rule violations (MissingImport:8, IfStatementAssignment:8, CyclomaticComplexity:6, NPathComplexity:5, UnusedFormalParameter:5)
Cpd Pass 0
Composer validate Info 4 valid; 4 advisory notes (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 34 34
2.4.8 35 35
2.4.9 35 35

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
OSL-3.0, AFL-3.0
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.