When using block settings to control when a block should go online, the cachelifetime header is set to the time when it is valid. This information would be great for application when they have there own caching so they know when they need to request the headless api again.
We currently implemented a listener which converts the TTL to a timestamp, else when just returning the TTL it would need to be calculated by AGE - CustomTTL header.
Maybe there are standard way (header) for things like gatsby or other JS libraries when a headless endpoint should be requested again to regenerate a site.
When using block settings to control when a block should go online, the cachelifetime header is set to the time when it is valid. This information would be great for application when they have there own caching so they know when they need to request the headless api again.
We currently implemented a listener which converts the TTL to a timestamp, else when just returning the TTL it would need to be calculated by
AGE - CustomTTL
header.Maybe there are standard way (header) for things like gatsby or other JS libraries when a headless endpoint should be requested again to regenerate a site.