Skip to content
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.

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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant