Unexpected caching strategy for /calendars/my/xxx

[dvcol]

Hello,

While other endpoints like /sync/history/ or/sync/watchlist/ are correctly cached as private, I've noticed that /calendars/my/ endpoints have a public caching strategy when I would expect data nested under the /my/ subpath to be segregated by user.

This leads to odd caching behaviors for my application where I support multiple concurrent signed-in users.

Is this expected behaviour?

This is not critical, as my current workaround is to invalidate cache on all of those calls (which could be further optimized by intelligently detecting which user is requesting by its token and strategically fetch with a reload strategy).

I would appreciate any input you could provide :)