Browser Cache TTL page rule value of Respect Existing Headers

Is it possible to have a page rule for Browser Cache TTL set to “Respect Existing Headers”? My Caching app has Browser Cache Level TTL set to 4 hours and I want a specific asset to respect existing headers so I can set alter the Browser Cache TTL based on the response (200 versus 404).

Yes, you would use “origin cache control” -> on for the page rule. But note that browsers won’t cache the “root” request, eg. if they load /index.html the browser won’t cache it whatsoever.

Thanks @Judge!

This topic was automatically closed after 30 days. New replies are no longer allowed.