Pages that receive a cache BYPASS

There'll always be some pages that you'll rarely ever want to cache. On some of these pages, we have default rules to ensure a BYPASS response is received to prevent any expected behaviour from breaking. Below is the list of subdomains and subdirectories that we'll force a cache BYPASS on.

  • /shop.*
  • /cart.*
  • /my-account.*
  • /checkout.*
  • /addons.*
  • /wp-admin/
  • /xmlrpc.php
  • wp-.*.php

For example, if you were to update your checkout URL to be a different URL to /checkout, the page may then cache which could cause problems with its behaviour.

If you need to update one of these specific URLs, you'll need to make sure you either set relevant cache-control directives in a .htaccess file OR add the new URL to the Exclusions list within StackCache (WordPress Admin > StackCache Exclusions).

  • CDN, cache, BYPASS, receive, Pages, StackCache
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How long is website data cached for at a CDN node?

The CDN itself is used to cache static content. By default, the following file types are cached...

What is the Website Acceleration Suite?

  Overview D2M Hosting's CDN powers-up your websites further by feeding them through our...

CDN Statistics

With the free D2M Hosting CDN, you can get an understanding about the traffic and requests...

Do I need caching plugins in addition to the D2M Hosting CDN?

The short answer is no, the D2M Hosting Content Delivery Network takes care of caching for you....

Does the D2M Hosting CDN perform cache warming?

Yes. The D2M Hosting CDN performs cache warming to ensure cached pages are served as frequently...

Powered by WHMCompleteSolution