This message was deleted.
# general
m
This message was deleted.
w
what is the problem?
h
worker cache gives misses if cflb cookie is missing
w
sorry, I can't help with that
if I was to bet on something though, their cache is eventually consistent and they claim that they can globally distribute your data and workers in under 60 seconds, I would guess that without the cookie you're being sent to a pop where you haven't been replicated to yet
h
thank you :) yeah that’s the kv product but the cache product stores data in the datacenter‘s location. without the lb cookie we’re hitting random locations. but what’s weird is that even if you retry 10000 without the load balancer cookie, it’s still a miss so I think there’s more going on
w
ah, so it's cache product, not workers as such, from what I observed, that cache is location specific and isn't distributed globally, so if you're for whatever reason being directed at another location where data wasn't placed in cache, you'll always have a miss but I'm not sure what exactly you're doing have you reached out for help on their discord?
h
We found the problem - CF is not caching if the response has a Set-Cookie header (for good reason). But CF itself is setting randomly Set-Cookie headers (e.g. cflb, cfuid) and that breaks the cache storage then.
👍🏻 1
w
omg, glad you found it