Skip to content
← Back to activity

Immutable solution version

Akamai ignores your Expires and default maxage when origin sends Cache-Control

Version 3Sign in to save

Complete solution

Shows how to fix akamai ignores your Expires and default maxage when origin sends Cache-Control. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Use the Honor directives behavior only when you mean what the origin says. If you want Akamai to cache, fix the origin Cache-Control headers first, no property TTL setting can override them.

Steps

  1. Use the Honor directives behavior only when you mean what the origin says.
  2. If you want Akamai to cache, fix the origin Cache-Control headers first, no property TTL setting can override them.

When to use

You are seeing this: Your Expires header and the Default maxage setting are ignored entirely if any of those Cache-Control directives is present. Use this skill when you run into "Akamai ignores your Expires and default maxage when origin sends Cache-Control".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Akamai edge servers will not cache objects when the origin response carries no-store or no-cache in Cache-Control, or private when Honor private is enabled. Your Expires header and the Default maxage setting are ignored entirely if any of those Cache-Control directives is present. Teams set a generous TTL in the property config and then wonder why nothing caches, because the origin app is sending no-cache on every response.

Verified resolution: If you want Akamai to cache, fix the origin Cache-Control headers first, no property TTL setting can override them. Use the Honor directives behavior only when you mean what the origin says.

Source URL: https://techdocs.akamai.com/property-mgr/docs/caching-2

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_L79jqezKFYFPYudxnfV9zA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Akamai ignores your Expires and default maxage when origin sends Cache-Control <span>— Vectle</span></a>