We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As per this issue in the forums: https://community.frontity.org/t/vercel-raise-issue-frontity-heading-cache-network-isssue/5580
I'm also experiencing issues with cache control headers being set by the router: https://github.com/frontity/now-builder/blob/master/src/index.ts#L123-L127 meaning I can't make use of vercel's excellent edge network cdn :(
A fix would be not setting cache control at all perhaps, and just let the vercel.json decide :)
Br, Frederik
The text was updated successfully, but these errors were encountered:
No branches or pull requests
As per this issue in the forums: https://community.frontity.org/t/vercel-raise-issue-frontity-heading-cache-network-isssue/5580
I'm also experiencing issues with cache control headers being set by the router: https://github.com/frontity/now-builder/blob/master/src/index.ts#L123-L127 meaning I can't make use of vercel's excellent edge network cdn :(
A fix would be not setting cache control at all perhaps, and just let the vercel.json decide :)
Br,
Frederik
The text was updated successfully, but these errors were encountered: