Akamai can store a copy of your content so the edge servers don’t have to keep going back to your origin servers to deliver content to your site visitors. This increases performance for your users, and reduces load and bandwidth on your origin web server.

Based on your site requirements, Akamai has already set you up with a good starting point for your caching settings. You can further customize these settings to increase your performance and ensure that you’re not caching any content that shouldn’t be cached.

The most common caching configurations are to not cache by default, and to choose which content should be cached. Check the provided list of common file extensions that typically can be cached, and add or subtract from this list as you see fit. You can also match on your URI paths that you’d like to cache. For example, /images/*.

The one exception, the default configuration for static sites, lets you cache everything by default, but also choose file extensions or path matches to exclude from caching. You can easily change the default rule from caching to not caching to suit your requirements.

OCA offers the basic caching settings. If you need more extensive caching settings, convert your property to Property Manager. If you want a deeper dive into caching in general, see What You Need to Know About Caching - Part 2.

Important information about caching and PCI

If you collect payments online, is your domain compliant with the Payment Card Industry (PCI) Data Security Standard (DSS)? Does your domain handle PCI information and is subject to PCI compliance? In addition to serving your content over the Akamai secure network, you'll want to review your caching settings and make sure you're not caching any credit card data.

The PCI DSS Configuration Guide on Control Center captures important details that you can use to configure your domain for PCI compliance.

Important information about caching PI content

How you handle personal information depends not only on the nature of the content but also on who it’s intended for. Say it’s financial statements or medical transcripts. If it’s intended for individual users, you shouldn’t cache it. On the other hand, if it’s intended to be shared by many users, caching may be appropriate. For example, some types of photos on social media may fall into this category according to European Union PI standards.

Important: Carefully review all of your cache settings under Configuration Settings to make sure you aren’t inadvertently caching any PI data that is not intended to be shared.

For example, suppose you are serving PI to users with URLs that look like this:

  • `/download/statement.pdf?id=29485'
  • `/download/statement.pdf?id=4951

In this case, to prevent caching you would create a cache path match on /download/statement.pdf* and set it to “Do Not Cache."

If you have a lot of PDF files that contain PI, you may want to ensure that any file with the PDF extension doesn’t get cached. As a general rule, the more specific you can be when identifying the PI content that shouldn’t be cached, the more total content can benefit by being cached.

Note: When intending PI content for a single user only, there’s not a lot to be gained by caching the content. However, if you want to cache PI content while still restricting access to authorized users, you can do so by using the advanced features available in Property Manager. Talk with your account team about implementing these features if you’re interested.