Title: Cache personalized responses now respect `max-age` values set at origin
Author: WordPress VIP Documentation
Published: October 21, 2025

---

 1. [Changelog](https://docs.wpvip.com/changelog/)
 2. [Infrastructure](https://docs.wpvip.com/changelog/infrastructure/)
 3. Cache personalized responses now respect `max-age` values set at origin

# Cache personalized responses now respect `max-age` values set at origin

---

 21 October 2025

20:30:47 GMT+0000

 [ Infrastructure ](https://docs.wpvip.com/changelog/infrastructure/)

 [ Permalink  ](https://docs.wpvip.com/changelog/infrastructure/cache-personalized-responses-now-respect-max-age-values-set-at-origin/)

Applications that leverage [the cache personalization API](https://docs.wpvip.com/caching/page-cache/the-vip-cache-personalization-api/)
can now specify a `max-age` value in the `Cache-Control` header returned by origins.

This value will be honored by the VIP edge, which will return a `Cache-Control` 
header with the `private` directive, to make sure only private caches can store 
the response, and the `max-age` directive containing the value set at origin.

### Changed

`Cache-Control` headers for responses that leverage cache personalization now include
the `max-age` value sent from origin, if available, instead of only specifying `
private`.