{ "title": "Host and cache compatibility", "seo_title": "Hosting and Cache Compatibility: Apache, Nginx, LiteSpeed", "h1": "Host and cache compatibility", "description": "Works on Apache, LiteSpeed, Nginx, IIS and Caddy, with LiteSpeed Cache, WP Rocket and WP Super Cache: built-in cache purges, Pro alias rules. Check yours.", "lead": "Apache, LiteSpeed, o2switch, Nginx, IIS, Caddy; LiteSpeed Cache, WP Rocket, WP Super Cache: built-in purges and, with Pro, alias rules tailored to your server.", "language": "en", "locale": "en-US", "type": "page", "url": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/", "canonical": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/", "markdown": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/index.md", "json": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/index.json", "published": "2026-10-27T23:16:48+00:00", "modified": "2026-11-05T20:53:41+00:00", "site": { "name": "WP Masquerade", "url": "https://www.wp-masquerade.com/" }, "translations": [ { "language": "en", "hreflang": "en-US", "title": "Host and cache compatibility", "url": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/", "markdown": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/index.md", "json": "https://www.wp-masquerade.com/features/hosting-and-cache-compatibility/index.json" }, { "language": "fr", "hreflang": "fr-FR", "title": "Compatibilité hébergeurs et caches", "url": "https://www.wp-masquerade.com/fr/fonctionnalites/compatibilite-hebergeurs-et-caches/", "markdown": "https://www.wp-masquerade.com/fr/fonctionnalites/compatibilite-hebergeurs-et-caches/index.md", "json": "https://www.wp-masquerade.com/fr/fonctionnalites/compatibilite-hebergeurs-et-caches/index.json" }, { "language": "es", "hreflang": "es-ES", "title": "Compatibilidad con hostings y cachés", "url": "https://www.wp-masquerade.com/es/funcionalidades/compatibilidad-hostings-y-caches/", "markdown": "https://www.wp-masquerade.com/es/funcionalidades/compatibilidad-hostings-y-caches/index.md", "json": "https://www.wp-masquerade.com/es/funcionalidades/compatibilidad-hostings-y-caches/index.json" }, { "language": "de", "hreflang": "de-DE", "title": "Kompatibel mit Hostern und Caches", "url": "https://www.wp-masquerade.com/de/funktionen/kompatibilitaet-hoster-und-caches/", "markdown": "https://www.wp-masquerade.com/de/funktionen/kompatibilitaet-hoster-und-caches/index.md", "json": "https://www.wp-masquerade.com/de/funktionen/kompatibilitaet-hoster-und-caches/index.json" }, { "language": "it", "hreflang": "it-IT", "title": "Compatibilità con hosting e cache", "url": "https://www.wp-masquerade.com/it/funzionalita/compatibilita-hosting-e-cache/", "markdown": "https://www.wp-masquerade.com/it/funzionalita/compatibilita-hosting-e-cache/index.md", "json": "https://www.wp-masquerade.com/it/funzionalita/compatibilita-hosting-e-cache/index.json" }, { "language": "pt", "hreflang": "pt-BR", "title": "Compatibilidade com hospedagens e cache", "url": "https://www.wp-masquerade.com/pt/recursos/compatibilidade-hospedagens-e-caches/", "markdown": "https://www.wp-masquerade.com/pt/recursos/compatibilidade-hospedagens-e-caches/index.md", "json": "https://www.wp-masquerade.com/pt/recursos/compatibilidade-hospedagens-e-caches/index.json" }, { "language": "nl", "hreflang": "nl-NL", "title": "Compatibel met hosting en cache", "url": "https://www.wp-masquerade.com/nl/functies/compatibiliteit-hosting-en-caches/", "markdown": "https://www.wp-masquerade.com/nl/functies/compatibiliteit-hosting-en-caches/index.md", "json": "https://www.wp-masquerade.com/nl/functies/compatibiliteit-hosting-en-caches/index.json" } ], "headings": [ { "level": 1, "text": "Host and cache compatibility" }, { "level": 2, "text": "Diagnostics that start with your server" }, { "level": 2, "text": "Ready-to-copy rules for each server (Pro)" }, { "level": 2, "text": "o2switch: built with TigerProtect in mind" }, { "level": 2, "text": "Page caches" }, { "level": 2, "text": "Plugin files that scanners can’t see" }, { "level": 2, "text": "Requirements" }, { "level": 2, "text": "Limitations and precautions" }, { "level": 3, "text": "Related reading" }, { "level": 2, "text": "Start free, upgrade to Pro when you’re ready" } ], "body": "## Diagnostics that start with your server\n\nThe **Diagnostics** tab shows the reported web server, your PHP and WordPress versions, installed plugins, mu-plugins, recognized caches and known conflicts. This inventory stays local: it is never sent to any third-party service.\n\n## Ready-to-copy rules for each server (Pro)\n\nThe [file URL aliases](https://www.wp-masquerade.com/features/file-url-aliases/) in WP Masquerade Pro need a server-side rewrite rule. Every other module, including the entire free version, works without any server rule. The plugin generates the exact block that matches your settings; it never edits your configuration files on its own.\n\n| Server | Where the rules go | What to check |\n| --- | --- | --- |\n| Apache 2.4 | .htaccess at the domain root | mod_rewrite and AllowOverride |\n| LiteSpeed Enterprise | Your host’s rewrite rules, often .htaccess | Order relative to the cache |\n| o2switch (PowerBoost) | .htaccess, at the very top, before # BEGIN LSCACHE and # BEGIN WordPress | Browser-based verification (TigerProtect) |\n| OpenLiteSpeed | Virtual host rewrite settings | A reload is often required |\n| Nginx | server block, before other rewrites | nginx -t, then reload |\n| IIS | system.webServer/rewrite/rules in web.config | URL Rewrite module, without replacing the file |\n| Caddy 2 | Ordered route before php_fastcgi and file_server | caddy validate, then reload |\n\nOn [managed hosting](https://www.wp-masquerade.com/glossary/managed-hosting/), just send the block to your server administrator.\n\n## o2switch: built with TigerProtect in mind\n\nOn o2switch, TigerProtect blocks requests a site makes to itself. WP Masquerade Pro detects this and verifies the aliases **from your browser** instead: each test file is downloaded and compared with the original. An “o2switch / PowerBoost” mode is available if automatic detection is unclear.\n\n## Page caches\n\n| Caching plugin | What WP Masquerade does | What you need to do |\n| --- | --- | --- |\n| LiteSpeed Cache | Purges through its API, marks login responses as non-cacheable | Exclude the login URL (Do Not Cache URIs) |\n| WP Rocket | Purges through its API | Exclude the login URL (Never Cache URL(s)) |\n| WP Super Cache | Purges through its API | Add the login URL to the rejected URL strings |\n| Other cache or CDN | Shown in the inventory | Purge with its own tool, exclude sensitive URLs |\n\nWith Pro, file URLs are also rewritten in the optimized output of LiteSpeed Cache and WP Rocket, as well as in inline scripts and JSON.\n\nA page served straight from a server cache or a [CDN](https://www.wp-masquerade.com/glossary/cdn/) never goes through WordPress, so the [security headers](https://www.wp-masquerade.com/features/security-headers/) sent by Pro and bot banning do not apply to it. The header check button shows what visitors actually receive.\n\n## Plugin files that scanners can’t see\n\nScanners spot plugins by requesting their `readme.txt` or translation files. WP Masquerade and WP Masquerade Pro each ship with an `.htaccess` file: on Apache, LiteSpeed and o2switch, their folder returns a 404 automatically. On Nginx, one line does the job:\n\n```\nlocation ~ ^/wp-content/plugins/cms-masquerade(-pro)?/(?!assets/) { return 404; }\n```\n\n## Requirements\n\n- WordPress 6.4 or later, PHP 7.4 or later;\n- **Single-site** WordPress: multisite is not supported;\n- the site and WordPress must share the same base URL; installs in a subfolder are supported.\n\n## Limitations and precautions\n\n- Use only one page caching engine. A purge request does not prove that every cache at your host or CDN is empty.\n- Having LiteSpeed Cache installed does not prove the server runs LiteSpeed: if in doubt, check with your host.\n- Never remove existing protections (PHP restrictions, private files, firewall) to get the aliases working.\n- Compatibility with every host, cache and plugin cannot be guaranteed: test on a copy of your site.\n\n**Behind Cloudflare?** Pro uses visitors’ real IP address, sent by Cloudflare and verified, for login attempt limiting, banning and logs. See [Cloudflare support](https://www.wp-masquerade.com/features/cloudflare/).\n\n### Related reading\n\n- [File URLs (aliases)](https://www.wp-masquerade.com/features/file-url-aliases/)\n- [Custom login page](https://www.wp-masquerade.com/features/custom-login-page/)\n- [Cloudflare support](https://www.wp-masquerade.com/features/cloudflare/)\n- [Best WordPress hosting compared](https://www.wp-masquerade.com/best-wordpress-hosting/)\n\n## Start free, upgrade to Pro when you’re ready\n\nThe free version already hides WordPress, moves the login page, blocks XML-RPC and counts bots. Pro locks down logins, renames file URLs and monitors your sites for you: known vulnerabilities, core integrity, activity log, email alerts and the update status of all your sites in your member area. From €59 per year excl. tax, far less than the cleanup offers whose prices we checked. [Compare the costs](https://www.wp-masquerade.com/pricing/#cout-piratage).\n\n[See Pro pricing](https://www.wp-masquerade.com/pricing/)\n\n[Download the free version](https://www.wp-masquerade.com/download/)", "format": "application/json" }