Should you use the cache API when requesting from R2?

I have a super simple worker wrapping R2.

This is the code so far:

export default {
    async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
        const url = new URL(request.url);
        const key = url.pathname.slice(1);

        
        const object = await env.MODRINTH_CDN.get(key);

        if (object === null) {
            return new Response(JSON.stringify({ error: 'not_found', description: 'the requested file does not exist' }), {
                status: 404,
                headers: {
                    'content-type': 'application/json',
                },
            });
        }

        const headers = new Headers();
        object.writeHttpMetadata(headers);
        headers.set('etag', object.httpEtag);

        return new Response(object.body, {
            headers,
        });
    },
};

export default {
    async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
        const url = new URL(request.url);
        const key = url.pathname.slice(1);

        
        const object = await env.MODRINTH_CDN.get(key);

        if (object === null) {
            return new Response(JSON.stringify({ error: 'not_found', description: 'the requested file does not exist' }), {
                status: 404,
                headers: {
                    'content-type': 'application/json',
                },
            });
        }

        const headers = new Headers();
        object.writeHttpMetadata(headers);
        headers.set('etag', object.httpEtag);

        return new Response(object.body, {
            headers,
        });
    },
};

export default {
    async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
        const url = new URL(request.url);
        const key = url.pathname.slice(1);

        
        const object = await env.MODRINTH_CDN.get(key);

        if (object === null) {
            return new Response(JSON.stringify({ error: 'not_found', description: 'the requested file does not exist' }), {
                status: 404,
                headers: {
                    'content-type': 'application/json',
                },
            });
        }

        const headers = new Headers();
        object.writeHttpMetadata(headers);
        headers.set('etag', object.httpEtag);

        return new Response(object.body, {
            headers,
        });
    },
};

export default {
    async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
        const url = new URL(request.url);
        const key = url.pathname.slice(1);

        
        const object = await env.MODRINTH_CDN.get(key);

        if (object === null) {
            return new Response(JSON.stringify({ error: 'not_found', description: 'the requested file does not exist' }), {
                status: 404,
                headers: {
                    'content-type': 'application/json',
                },
            });
        }

        const headers = new Headers();
        object.writeHttpMetadata(headers);
        headers.set('etag', object.httpEtag);

        return new Response(object.body, {
            headers,
        });
    },
};

Do I have to use the Cache API to use the cloudflare CDN to cache the assets on R2? Or is that automatic. This cache API: https://developers.cloudflare.com/workers/examples/cache-api/. Or should I put a page rule in front of this saying to cache things

Using the Cache API · Cloudflare Workers docs

Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones …

GGeometrically I have a super simple worker wrapping R2. This is the code so far: ```ts export...

Chaika•11/4/23, 12:14 AM

Do I have to use the Cache API to use the cloudflare CDN to cache the assets on R2? Or is that automatic

Yes, you need to use the Cache API

Or should I put a page rule in front of this saying to cache things

Cache doesn't run in front of workers, no matter how many page/cache rules you set

Chaika•11/4/23, 12:15 AM

Well, to clarify: The assets are already on R2, you wouldn't be "caching on R2", but instead caching on the edge

GeometricallyOP•11/4/23, 12:15 AM

Yup that's what I mean

GeometricallyOP•11/4/23, 12:15 AM

Thanks!

Chaika•11/4/23, 12:15 AM

Any requests which hit edge cache don't cost you anything, no Class Bs, other then the Worker invocation cost

Chaika•11/4/23, 12:16 AM

If you can use R2's Custom Domain feature, you can even get away from those.
If you need to use a worker, you could look into this library here: https://github.com/kotx/render which does cache/etc for you, can hook into it like a library

GeometricallyOP•11/4/23, 12:19 AM

thanks!!

GeometricallyOP•11/4/23, 12:20 AM

yeah we use custom domains rn but we're doing some more complex stuff now so converting it to a worker

GeometricallyOP•11/4/23, 1:00 AM

@Chaika Sorry for the ping, but does stuff like polish run in front of workers?

GGeometrically @Chaika Sorry for the ping, but does stuff like polish run in front of workers?

Chaika•11/4/23, 1:03 AM

I don't remember the exact details, but it looks like my R2 Worker does use polish after the image gets cached and a few hits, it's a function of cache I guess

GeometricallyOP•11/4/23, 1:03 AM

gothca thx

CChaika I don't remember the exact details, but it looks like my R2 Worker does use poli...

GeometricallyOP•11/4/23, 1:10 AM

does cache work in local testing? it's not working for me. i read somewhere you need a custom domain under cloudflare, is that also true for local?

GGeometrically does cache work in local testing? it's not working for me. i read somewhere you ...

Chaika•11/4/23, 1:11 AM

Requires Custom Domain yea, I would assume it doesn't work for --remote dev either, not sure about local local though

However, any Cache API operations in the Cloudflare Workers dashboard editor, Playground previews, and any *.workers.dev deployments will have no impact. For Workers fronted by Cloudflare Access
, the Cache API is not currently available. Only Workers deployed to custom domains have access to functional cache operations.

https://developers.cloudflare.com/workers/runtime-apis/cache/

CChaika Requires Custom Domain yea, I would assume it doesn't work for --remote dev eith...

GeometricallyOP•11/4/23, 1:12 AM

gotcha, is there an easy way to write to my local "r2 bucket"?

Chaika•11/4/23, 1:13 AM

You can use wrangler r2 commands like wrangler r2 object put <OBJECT_PATH> [OPTIONS] with the --local flag to interact with local
https://developers.cloudflare.com/workers/wrangler/commands/#r2-object

Chaika•11/4/23, 1:13 AM

it's a bit weird since you don't need --local for dev but you do for the commands but it is there lol

CChaika You can use wrangler r2 commands like wrangler r2 object put <OBJECT_PATH> [OPTI...

GeometricallyOP•11/4/23, 1:22 AM

himm for me it says --local doesnt exist

GeometricallyOP•11/4/23, 1:22 AM

wrangler r2 object put modrinth-cdn-staging/test.txt --file wrangler.toml --localwrangler r2 object put modrinth-cdn-staging/test.txt --file wrangler.toml --local

GeometricallyOP•11/4/23, 1:22 AM

this is my command

GeometricallyOP•11/4/23, 1:25 AM

oh nvm

GeometricallyOP•11/4/23, 1:25 AM

my wrangler was out of date

Should you use the cache API when requesting from R2?

Similar Threads

Similar Threads

Similar Threads