cacheKey usage In workers

Hi!

We are using workers and using fetch to perform image resizing. We have our own version control over images so we are using cacheKey in order to invalidate the cache whenever our version changes. I do see the following behavior:

When trying to fetch an ipfs image, we use an ipfs gateway which works very fast and supposed to be cached on cloudflare but when I force the fetch to use the original ipfs url I still get a timeout from the worker even through i would expect the response to return immediately as the cacheKey is the same. It seems the original is always being called and the options are ignored.

Here are the options I am passing to the fetch:
“{
cf: {
cacheEverything: true,
cacheTtl: 86400 * 365, // 1 year
cacheKey: CACHE_KEY_VALUE,
},
}”

How can I validate the cacheKey is being utilized?