Skip to content

Add cacheability to metastore response. - #4782

Draft
swirtSJW wants to merge 1 commit into
4.xfrom
add-metastore-response-caching
Draft

Add cacheability to metastore response.#4782
swirtSJW wants to merge 1 commit into
4.xfrom
add-metastore-response-caching

Conversation

@swirtSJW

@swirtSJW swirtSJW commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Fixes #4783

Describe your changes

These changes are an initial stab at defining caching. Discussion is probably needed about the ideal numbers for caching.

QA Steps

  • Add manual QA steps in checklist format for a reviewer to perform. Be as specific as possible, provide examples if appropriate.

Checklist before requesting review

If any of these are left unchecked, please provide an explanation

  • I have updated or added tests to cover my code
  • I have updated or added documentation

// Actively declare cacheable. Otherwise Drupal core will add 'no-cache'.
$response->headers->set(
'Cache-Control',
'public, max-age=3600, s-maxage=86400'

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The numbers might need some tweaking.

@swirtSJW
swirtSJW marked this pull request as draft September 2, 2026 03:35
@swirtSJW

swirtSJW commented Sep 2, 2026

Copy link
Copy Markdown
Contributor Author

There is limits to what can be tested locally. Willl have to deploy to an acquia environment to truly test it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Metastore API response should be cacheable to get picked up by Akamai

1 participant