Cache doesn't support the cf:{cacheKey: 'cacheKeyHere'} property of a request

[cdloh]

An undocumented, but supported, feature of the cache API is the ability to supply custom cache keys via the CF object of a request

eg

let cacheKey = new Request(request, {
        'method': request.method,
        'headers': request.headers,
        'body': (request.method == 'GET' || request.method == 'HEAD' ) ? null : request.body,
        'cf': {
            'cacheKey': getCacheKey(request),
            'reallyUseCacheKey': true,
        }
    });

We use this pretty extensively within our workers. Happy to take a punt at adding it if you're willing to support it?

I'd understand if you wouldn't want to given it's largely undocumented support.

[mrbbot]

Hey! 👋 This should definitely be supported. In your example, is cacheKey what you pass to the first argument of cache.put/match/delete? Also is reallyUseCacheKey a real parameter 😆? What does it do?

[cdloh]

It is a real parameter. At the time that we wrote the worker it was required for the worker to respect the cacheKey however I've just deployed a new version of the worker without it to test and it appears to no longer be required.

[mrbbot]

Hey! 👋 The first pre-release of Miniflare 2 has just been released, including support for cf.cacheKey, cf.cacheTtl and cf.cacheTtlByStatus. You can find the full changelog here and install it with npm i miniflare@next -D. Please let me know if you have any other issues, and feel free to ask questions in the #miniflare channel of the Cloudflare Workers Discord server.