Caching urls with side effects like a user browsing history.
Is it possible for, when cloudflare responds to a request with a cached response, forward the requested url in some forms so analytics, user history, ect can be coded to work even though the origin never saw the request? (would just need to give the user an auth token or some other identifying thing) Atm we avoid caching through servers we dont control, but if there some way our origins could still know what the user did it would work fine since most of our URLs are deterministic given a set of query strings... its just they can have side effects and if the cache responds the origin wouldnt know to do them.
0 Replies