Configure individual Cloudflare rules for website pages

You can set up individual Cloudflare rules for website pages. The rules will be executed even if they do not match the global settings for a domain zone.

To create a rule for the page:

1. Log in to ISPmanager as the User.
2. Check that the domain is connected to Cloudflare. For more information please refer to the article Connect a domain to Cloudflare.
3. Go to Tools → Cloudflare → Page rules → Add.
4. Enter the Page address that the rule will be created for.
5. To redirect to another page:
   1. Enable the option Redirect.
   2. Enter the Destination.
   3. Enter the Return code.
6. Enable the HTTPS option to redirect to the secure protocol.
   Note.

   You can provide the page settings only if the options Redirect and HTTPS are disabled.
7. After you have enabled the option Always online, when your server goes down, Cloudflare will serve pages from its cache, so visitors still see some of the pages they are trying to visit.
8. Enable the option Automatic HTTPS rewrites to rewrite links to unencrypted resources from HTTP to HTTPS.
9. In the Browser TTL field you can specify how long in seconds resources cached by client browsers remain valid.
10. Browser integrity check — this option allows Cloudflare to look for common HTTP headers abused most commonly by spammers and denies access to your page. It will also challenge visitors that do not have a user agent or a non-standard user agent. Access will be blocked if the threat is detected.
11. Set the page Caching level:
    • Disabled — disable caching;
    • No query string — only delivers resources from the cache when there is no query string;
    • Ignore query string — delivers the same resource to everyone independent of the query string;
    • With query parameters — delivers a different resource each time the query string changes;
    • Cache all — cache all data.
12. In the Disable functions  field select the functions that will be disabled for the field: 
    • Protection — disable Email Obfuscation", SSE (Server Side Excludes), WAF, Rate Limiting, and Web scraping (Scrape Shield);
    • Performance improvement — disable Minification, Rocket Loader, Mirage, Polish;
    • Applications — disable all Cloudflare applications.
13. Select the checkbox Email obfuscation to hide email addresses on your web page from bots while keeping them visible to humans.
14. Select a Security level:
    • Off;
    • Under attack — this level is used when your website is under DDoS attack;
    • High — challenge all of the users detected as offending in the past 14 days;
    • Medium — challenge users who pose some threat;
    • Low — challenge users who pose the greatest threat;
    • Essentially off — challenge only the most abusive users.
15. Enable the option SSE if you want to hide sensitive content on your website from suspicious visitors. You will need to wrap the content with the following tags . E.g.:

    Hidden content

    <!--sse-->Hiddent content<!--/sse-->

16. Set an SSL certificate for the domain to establish an encrypted link between a web server and a browser:
    
    • Off — no secure connection between your visitor and Cloudflare, and no secure connection between Cloudflare and your web server either. This means that visitors can only view your website over HTTP;
    • Self-signed — secure connection between visitors and Cloudflare, and secure connection (but not authenticated) between Cloudflare and your web server;
    • Flexible — choose this option, if your origin web-server cannot accept secure (HTTPS) connections. Visitors will be able to access HTTPS, but requests to the web-server will be sent through HTTP;
    • Existing — secure connection between visitors and Cloudflare, and secure and authenticated connection between Cloudflare and your web server.
17. Click on Ok to save the changes in Cloudflare.