Improve catch-all rewriter caching strategy #36
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#34 introduced a catch-all route handler that acts as a fallback rewriter for our content pages. It had implementations of caching mechanisms, but these did not seem to work as expected in production.
This pr introduces the use of
generateStaticParamsto cache route invocations for the paths present in oursitemapon build time, which results in instant server responses on our rewritten pages.