You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The http.send function caches/memoizes responses using the method and url as the key. The problem is that for non-restful APIs this will result in incorrect answers. The http.send function should default to performing a comparison on all function parameters. If this becomes too expensive we could add an optional cache key parameter in the future.
The text was updated successfully, but these errors were encountered:
tsandall
changed the title
http.send caching should incorporate headers/body
http.send caching should incorporate all params in key
Jan 3, 2020
Previously it just used a string key with the method and url. This
causes problems if headers or body contents affect the response, and
users were seeing cached responses returned for different requests.
The new version takes into account the entire parameters object that
is provided to the builtin function.
Fixes: open-policy-agent#1980
Signed-off-by: Patrick East <east.patrick@gmail.com>
Previously it just used a string key with the method and url. This
causes problems if headers or body contents affect the response, and
users were seeing cached responses returned for different requests.
The new version takes into account the entire parameters object that
is provided to the builtin function.
Fixes: #1980
Signed-off-by: Patrick East <east.patrick@gmail.com>
The
http.send
function caches/memoizes responses using the method and url as the key. The problem is that for non-restful APIs this will result in incorrect answers. Thehttp.send
function should default to performing a comparison on all function parameters. If this becomes too expensive we could add an optional cache key parameter in the future.The text was updated successfully, but these errors were encountered: