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

Optimize genlocks usage #19

Merged
merged 2 commits into from
Apr 1, 2021
Merged

Optimize genlocks usage #19

merged 2 commits into from
Apr 1, 2021

Commits on Mar 29, 2021

  1. Optimize genlocks usage

    Currently many requests unnecesarily get no batcache serving or headers set due to over-generic genlocks. At the moment a single genlock goves a url path, like `/wp/v2/posts`, which means any requests to `/wp/v2/posts?per_page=1` will not get cached, or send cache headers while the first request to `/wp/v2/posts` is processing.
    
    I see no reason why genlocks and versions should not be tracked against the exact batcache cache key, rather than URL-only.
    joehoyle committed Mar 29, 2021
    Configuration menu
    Copy the full SHA
    befe5ab View commit details
    Browse the repository at this point in the history

Commits on Apr 1, 2021

  1. Configuration menu
    Copy the full SHA
    5e8fbb7 View commit details
    Browse the repository at this point in the history