Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[⚡ Feature]: Implement next-suspense-cache header #786

Open
1 task
WalshyDev opened this issue May 14, 2024 · 0 comments · May be fixed by #787
Open
1 task

[⚡ Feature]: Implement next-suspense-cache header #786

WalshyDev opened this issue May 14, 2024 · 0 comments · May be fixed by #787
Labels
enhancement New feature or request

Comments

@WalshyDev
Copy link
Member

Description

The suspense cache is currently a bit of a black box, customers don't know it's happening and cannot see if users are being served cached content.

I'd like for us to add a next-suspense-cache header which will have HIT/MISS/DYNAMIC (? e.g. disabled) so customers can know quickly and easily.

This diverges slightly from Next however, given the current black box behaviour and the fact customers keep running up against it I think it's more than fair to do this.

Additional Information

No response

Would you like to help?

  • Would you like to help implement this feature?
@WalshyDev WalshyDev added the enhancement New feature or request label May 14, 2024
@james-elicx james-elicx linked a pull request May 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant