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

Eval endpoint cache control #12

Open
asdine opened this issue Oct 19, 2018 · 0 comments
Open

Eval endpoint cache control #12

asdine opened this issue Oct 19, 2018 · 0 comments
Labels
bug Something isn't working
Milestone

Comments

@asdine
Copy link
Contributor

asdine commented Oct 19, 2018

To avoid having the result of the eval action being cached by proxies or browsers when evaluating the latest version of a ruleset, we need to add the right HTTP headers to control the caching policy:

  • GET /rulesets/some-path?eval&param1=1&param2=2 -> latest version -> no http caching (or etag)
  • GET /rulesets/some-path?eval&version=xyz&param1=1&param2=2 specific version -> http caching
@asdine asdine added the bug Something isn't working label Oct 19, 2018
@asdine asdine added this to the v0.6.0 milestone Oct 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant