yeah i have a custom r2 domain, but when doing bindings is that domain used ? - Cloudflare Developers

© 2026 Hedgehog Software, LLC

More

Communities Docs About Terms Privacy

Chaika

C

Chaika•2/2/24, 12:58 AM

If you use an R2 Custom Domain then you wouldn't pay for Worker Invocations and any cache hits are free

bun

Bbun yeah i have a custom r2 domain, but when doing bindings is that domain used ?

Chaika

C

Chaika•2/2/24, 12:58 AM

what do you mean "when doing bindings"?

bun

B

bunOP•2/2/24, 12:59 AM

i wasnt accessing r2 storage through fetch on my custom domain. i was accessing them through

wrangler.toml

wrangler.toml

storage bindings

Chaika

C

Chaika•2/2/24, 1:00 AM

That wouldn't use the Custom domain or cache by default, you'd have to use the cache api yourself

Chaika

C

Chaika•2/2/24, 1:01 AM

i couldnt get it to work, i would get cache miss everytime

The Cache API doesn't work/will always return miss in a bunch of environments, including dev

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/

bun

B

bunOP•2/2/24, 1:01 AM

yeah i was doing the cache api manually but it wasnt working for some reason

bun

B

bunOP•2/2/24, 1:01 AM

yeah my workers were also deployed with custom domains

bun

B

bunOP•2/2/24, 1:01 AM

i can show you my code if that will help

Chaika

C

Chaika•2/2/24, 1:01 AM

Sure

bun

B

bunOP•2/2/24, 1:02 AM

app.use("*", async (c, next) => {
  const t = performance.now();
  const cache = caches.default;

  const cacheUrl = new URL(c.req.url);

  const cacheKey = new Request(cacheUrl.toString(), c.req);

  let response = await cache.match(cacheKey);

  if (response) {
    c.env.myData = { cachedData: await response.json() };
    console.log("cache hit", performance.now() - t);
    return next();
  }

  const object = await c.env.MY_R2_STORAGE.get("some-data.json");

  if (!object) {
    throw new Error("Data not found");
  }

  const headers = new Headers();

  object.writeHttpMetadata(headers);
  headers.set("etag", object.httpEtag);
  const status = object.body ? 200 : 304;

  const [body1, body2] = object.body.tee();

  response = new Response(body1, {
    headers,
    status,
  });

  response.headers.append("Cache-Control", "s-maxage=31536000");

  c.executionCtx.waitUntil(cache.put(cacheKey, response));

  if (!cachedData) {
    throw new Error("Data not found");
  }

  c.env.myData = { cachedData: await streamToJson(body2) };

  console.log("cache miss", performance.now() - t);

  return next();
});

app.use("*", async (c, next) => {
  const t = performance.now();
  const cache = caches.default;

  const cacheUrl = new URL(c.req.url);

  const cacheKey = new Request(cacheUrl.toString(), c.req);

  let response = await cache.match(cacheKey);

  if (response) {
    c.env.myData = { cachedData: await response.json() };
    console.log("cache hit", performance.now() - t);
    return next();
  }

  const object = await c.env.MY_R2_STORAGE.get("some-data.json");

  if (!object) {
    throw new Error("Data not found");
  }

  const headers = new Headers();

  object.writeHttpMetadata(headers);
  headers.set("etag", object.httpEtag);
  const status = object.body ? 200 : 304;

  const [body1, body2] = object.body.tee();

  response = new Response(body1, {
    headers,
    status,
  });

  response.headers.append("Cache-Control", "s-maxage=31536000");

  c.executionCtx.waitUntil(cache.put(cacheKey, response));

  if (!cachedData) {
    throw new Error("Data not found");
  }

  c.env.myData = { cachedData: await streamToJson(body2) };

  console.log("cache miss", performance.now() - t);

  return next();
});

bun

B

bunOP•2/2/24, 1:04 AM

as you can see i was using same cacheKeycacheKey for both cache.matchcache.match and

cache.put

cache.put

. however it was always a miss

bun

B

bunOP•2/2/24, 1:05 AM

im super confused on why

Request

Request

constructed from request.urlrequest.url has to be the cache key

Chaika

C

Chaika•2/2/24, 1:08 AM

Its built on top of the normal cdn cache

Chaika

C

Chaika•2/2/24, 1:09 AM

it could be a valid url that isn't in your zone as long as it's not another cf website, some people use example.invalid or stuf like that

Chaika

C

Chaika•2/2/24, 1:09 AM

if you pass it a request with headers though it respects some of them: https://developers.cloudflare.com/workers/runtime-apis/cache/#parameters-1

Cache · Cloudflare Workers docs

Control reading and writing from the Cloudflare global network cache.

Chaika

C

Chaika•2/2/24, 1:21 AM

I don't see anything wrong with that code though as long as it is running on a custom domain/route on your own domain (i.e not the workers.dev, not behind access.
It just never returns hit on your end?
I would question though if it's the same response json, why are you having it differ by url?

bun

B

bunOP•2/2/24, 1:24 AM

differ by url? you mean const cacheUrl = new URL(c.req.url)const cacheUrl = new URL(c.req.url) ?

bun

B

bunOP•2/2/24, 1:24 AM

yeah i was just super confused by this methodology of caching something so while trying to make it work i just didnt question it and made it as close to the documentation example as possible

bun

B

bunOP•2/2/24, 1:25 AM

const request = await fetch("https://r2.sunney.dev/data.json", {
    cf: {
      cacheTtl: 60 * 60 * 24,
      cacheEverything: true,
      cacheKey: someCustomKey,
    },
  }).then((res) => res.json());

const request = await fetch("https://r2.sunney.dev/data.json", {
    cf: {
      cacheTtl: 60 * 60 * 24,
      cacheEverything: true,
      cacheKey: someCustomKey,
    },
  }).then((res) => res.json());

this works well enough

Chaika

C

Chaika•2/2/24, 1:27 AM

same cache anyway, that'll work. Embedding it in a Worker isn't a bad idea either, I do that for html just for fun & speed and it works well, super fast

bun

B

bunOP•2/2/24, 1:27 AM

thanks for all the help

dave

D

dave•2/2/24, 5:05 AM

if I wanna gzip things before putting them into R2, do I really have to await on the response?

dave

D

dave•2/2/24, 5:06 AM

if I don't, it complains that the content length is not known

Rahul Raikwar

R

Rahul Raikwar•2/2/24, 12:12 PM

How can achieve this - setting up a webhook in next js project to automatically trigger builds on Cloudflare when changes shopify admin products, collections, blog articles, and pages.

Original message was deleted

Isaac McFadyen

I

Isaac McFadyen•2/2/24, 1:15 PM

Yes.

Isaac McFadyen

I

Isaac McFadyen•2/2/24, 1:16 PM

Not sure if there's a publicly stated reason but I'd just consider the fact that some Workers customers get millions of requests per second - at that scale, decompressing the Worker itself isn't an insignificant cost and I assume they preferred decompression speed over size.

Isaac McFadyen

I

Isaac McFadyen•2/2/24, 1:17 PM

It would also be a fairly major task to switch over to a new algorithm considering they'd need to decompress and recompress thousands of old Workers and switch all of the runtime components to the new algorithm across thousands of servers, all without any downtime.

peshakoo

Ppeshakoo Hey Dave! if you don't mind could you show me how you did this?? I'm doing somet...

dave

D

dave•2/2/24, 2:12 PM

Hmm lemme check if we actually ended up doing it or not. ;p

Original message was deleted

dave

D

dave•2/2/24, 2:14 PM

Likely they use Workers for some of the Workers supporting infrastructure. Workers only support compressing gzip streams. https://developer.mozilla.org/en-US/docs/Web/API/CompressionStream/CompressionStream

peshakoo

Ppeshakoo Hey Dave! if you don't mind could you show me how you did this?? I'm doing somet...

dave

D

dave•2/2/24, 2:19 PM

ah sorry, we ended up not needing to use ListObjects. That said, I think it should be pretty straightforward, would be a cool blog post if you end up doing it

Original message was deleted

dave

D

dave•2/2/24, 2:20 PM

Yes, but maintaining an-out-of-tree patch to V8 and making a non-standard Web API kinda sucks

Original message was deleted

dave

D

dave•2/2/24, 2:25 PM

pretty sure they did a blog post on it

Original message was deleted

dave

D

dave•2/2/24, 2:28 PM

https://blog.cloudflare.com/deploying-firmware-at-cloudflare-scale-how-we-update-thousands-of-servers-in-more-than-285-cities

Original message was deleted

dave

D

dave•2/2/24, 2:28 PM

https://blog.cloudflare.com/anchoring-trust-a-hardware-secure-boot-story

The Cloudflare Blog

Anchoring Trust: A Hardware Secure Boot Story

As a security company, we pride ourselves on finding innovative ways to protect our platform to, in turn, protect the data of our customers. Part of this approach is implementing progressive methods in protecting our hardware at scale.

Original message was deleted

Chaika

C

Chaika•2/2/24, 2:29 PM

They're just Linux machines. Their main inbound proxy is just nginx (modified though of course), they made some of their patches public. Workers use workerd to run (https://github.com/cloudflare/workerd), built on top of Chromium's V8 Javascript Engine, nothing too crazy

Chaika

C

Chaika•2/2/24, 2:29 PM

they go over a lot of it in their blogs like the ones linked above

Chaika

C

Chaika•2/2/24, 2:29 PM

also Cloudflare lol

Mehanika

M

Mehanika•2/2/24, 2:34 PM

Anyone successfully integrated Sentry and their Worker? I added the projects but they dont show up on the list for reasons unknown

Screenshot_2024-02-02_at_15.34.03.png

Chaika

C

Chaika•2/2/24, 2:36 PM

per account

Original message was deleted

Mehanika

M

Mehanika•2/2/24, 2:37 PM

Thanks!

Original message was deleted

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:13 PM

Hash it?

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:13 PM

There is a chance of collision, but with a good enough algo, it would be pretty small

Original message was deleted

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:15 PM

Unless you are willing to compute the hash for every IP, it should still be fine, no?

Original message was deleted

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:16 PM

You could, but that Worker secret can still be retrieved by said Worker, then exfiltrated

Original message was deleted

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:16 PM

Not in the dash, but you can just publish a new version of the Worker that returns the secret as a header or something

Original message was deleted

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:17 PM

Salt it with the geolocation info of the IP?

Hello, I’m Allie!

H

Hello, I’m Allie!•2/2/24, 3:17 PM

So city country coords etc

const request = await fetch("https://r2.sunney.dev/data.json", {
    cf: {
      cacheTtl: 60 * 60 * 24,
      cacheEverything: true,
      cacheKey: someCustomKey,
    },
  }).then((res) => res.json());

const request = await fetch("https://r2.sunney.dev/data.json", {
    cf: {
      cacheTtl: 60 * 60 * 24,
      cacheEverything: true,
      cacheKey: someCustomKey,
    },
  }).then((res) => res.json());

app.use("*", async (c, next) => {
  const t = performance.now();
  const cache = caches.default;

  const cacheUrl = new URL(c.req.url);

  const cacheKey = new Request(cacheUrl.toString(), c.req);

  let response = await cache.match(cacheKey);

  if (response) {
    c.env.myData = { cachedData: await response.json() };
    console.log("cache hit", performance.now() - t);
    return next();
  }

  const object = await c.env.MY_R2_STORAGE.get("some-data.json");

  if (!object) {
    throw new Error("Data not found");
  }

  const headers = new Headers();

  object.writeHttpMetadata(headers);
  headers.set("etag", object.httpEtag);
  const status = object.body ? 200 : 304;

  const [body1, body2] = object.body.tee();

  response = new Response(body1, {
    headers,
    status,
  });

  response.headers.append("Cache-Control", "s-maxage=31536000");

  c.executionCtx.waitUntil(cache.put(cacheKey, response));

  if (!cachedData) {
    throw new Error("Data not found");
  }

  c.env.myData = { cachedData: await streamToJson(body2) };

  console.log("cache miss", performance.now() - t);

  return next();
});

app.use("*", async (c, next) => {
  const t = performance.now();
  const cache = caches.default;

  const cacheUrl = new URL(c.req.url);

  const cacheKey = new Request(cacheUrl.toString(), c.req);

  let response = await cache.match(cacheKey);

  if (response) {
    c.env.myData = { cachedData: await response.json() };
    console.log("cache hit", performance.now() - t);
    return next();
  }

  const object = await c.env.MY_R2_STORAGE.get("some-data.json");

  if (!object) {
    throw new Error("Data not found");
  }

  const headers = new Headers();

  object.writeHttpMetadata(headers);
  headers.set("etag", object.httpEtag);
  const status = object.body ? 200 : 304;

  const [body1, body2] = object.body.tee();

  response = new Response(body1, {
    headers,
    status,
  });

  response.headers.append("Cache-Control", "s-maxage=31536000");

  c.executionCtx.waitUntil(cache.put(cacheKey, response));

  if (!cachedData) {
    throw new Error("Data not found");
  }

  c.env.myData = { cachedData: await streamToJson(body2) };

  console.log("cache miss", performance.now() - t);

  return next();
});