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
Not sure if this is a bug or something which should be added to the documentation.
When caching requests the cache key is based on a couple of request headers (#558). I'm assuming this works fine when using AUTH_ACCESS_TOKEN for authentication as this token does not change.
When authenticating as an integration it's required to include a JSON Web Token which is valid for a few seconds up to a couple of minutes (I think 10 minutes is the limit). I'm always including a new JWT token which works fine but I'm guessing this is causing trouble with caching since the cache key is changing on every request because the Authorization header has changed (new JWT token).
Replacing the Authorization header on the HeaderCacheKeyGenerator with the installation id seems like a good alternative:
Not sure if this is a bug or something which should be added to the documentation.
When caching requests the cache key is based on a couple of request headers (#558). I'm assuming this works fine when using
AUTH_ACCESS_TOKEN
for authentication as this token does not change.When authenticating as an integration it's required to include a JSON Web Token which is valid for a few seconds up to a couple of minutes (I think 10 minutes is the limit). I'm always including a new JWT token which works fine but I'm guessing this is causing trouble with caching since the cache key is changing on every request because the Authorization header has changed (new JWT token).
Replacing the Authorization header on the HeaderCacheKeyGenerator with the installation id seems like a good alternative:
Not sure if there is a better alternative to fix this.
Let me know if you want me to create PR to update the documentation.
The text was updated successfully, but these errors were encountered: