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 topic of caching hasn't been covered in here, so wanted to check on it. Interested to know about the best practice around cache-control response headers when serving a JSWK. Is it generally advised to not cache these at all to keep the content stale or having a short max-age (like one day) is acceptable? Was trying to find a reference material on this topic, but there doesn't seem to be anything in the RFC 7517.
Edit: found in the documentation that Apigee does "The data for the current key and JWKS is cached in the Apigee gateway, for 180s". Wondering where the 180s period is taken from?
The text was updated successfully, but these errors were encountered:
The topic of caching hasn't been covered in here, so wanted to check on it. Interested to know about the best practice around
cache-control
response headers when serving a JSWK. Is it generally advised to not cache these at all to keep the content stale or having a short max-age (like one day) is acceptable? Was trying to find a reference material on this topic, but there doesn't seem to be anything in the RFC 7517.Edit: found in the documentation that Apigee does "The data for the current key and JWKS is cached in the Apigee gateway, for 180s". Wondering where the 180s period is taken from?
The text was updated successfully, but these errors were encountered: