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
{{ message }}
Repository navigation
The caching feature does not say that a value created for one request must never be cached #47
The caching feature says how a cache key is made from Evidence, but not that some results hold a value created for the one request that asked for it. A 51Did is one. The cloud service creates a new 51Did for every request, so two requests with identical Evidence receive different 51Dids, and a cache that stores the Cloud Request Engine's response hands the 51Did created for one request to the next request with the same Evidence.
Say that a cache MUST NOT store, or serve, a result that holds such a value, and how the Cloud Request Engine applies that to a response carrying a fodid member.
Fixed on main (6570727, #134): caching.md line 144 says "A cache MUST NOT store a result that holds such a value, and MUST NOT serve one that it finds", with the 51Did case at lines 146 to 149.
Activity
jwrosewell commentedon Nov 13, 2026
Fixed on main (6570727, #134): caching.md line 144 says "A cache MUST NOT store a result that holds such a value, and MUST NOT serve one that it finds", with the 51Did case at lines 146 to 149.