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
First of all, thanks a lot for this project, it's basically exactly what I was looking for! 🙌
However, I encountered some limitations quite soon. I'd like to have more options for configuring the keys by which objects are cached.
My use case at hand is to cache user-specific responses, so that for authenticated requests to the same route, different content is returned for different users. I see two possible solutions to this:
Consider request headers in cache key. Some (-> make this configurable) headers could be included to the key when writing to or reading from the cache, e.g. the Authorization header's contents.
Add user-defined key elements. A more generic solution is to allow the developer to specify custom values to consider as part of the cache key. Something like this:
First of all, thanks a lot for this project, it's basically exactly what I was looking for! 🙌
However, I encountered some limitations quite soon. I'd like to have more options for configuring the keys by which objects are cached.
My use case at hand is to cache user-specific responses, so that for authenticated requests to the same route, different content is returned for different users. I see two possible solutions to this:
Authorization
header's contents.The text was updated successfully, but these errors were encountered: