# Blacklist with CDN
Content that musn't be marfeelized is usually blacklisted in the definition.json.
For tenants using MarfeelCDN, the CDN must also blacklist the same page, to guarantee Marfeel doesn't interfere, whether it is with marfeelization or cache.
CDN Blacklisting relies on different flags, for different strategies. For pages that shouldn't be marfeelized, you can use blacklistURL and the same regular expression as in the definition.json.
# Avoid caching
Tenants can manage resources that should not be cached at all but can go through MarfeelCDN.
To do so, they can set a specific cache-control header on those resources, marking them private.
Read more about cache-control and private.
TIP
MarfeelCDN becomes useless if all of a tenant's pages are marked private. Article pages and "normal" resources must be public to benefit from MarfeelCDN performance improvements.
# Website admin panel
MarfeelCDN should never interfere with backend requests. This means all requests to the tenant's CMS should be blacklisted by MarfeelCDN.
MarfeelCDN automatically blacklists the default WordPress admin panel, under example.com/wp-admin.
For any other CMS, action is required, with information from the tenant:
- The base URL of the CMS admin
- Or, if it doesn't have one like for Drupal, the login cookie.
With that information, configure blacklistCookie or blacklistURL appropriately.
TIP
If the tenant's CMS is:
- On another domain,
- Or on a subdomain, like admin.example.com
No action is required.