sorry, meant `( request.headers.get( 'cookie' ) || '' ).includes`*

A

alexOP•5/24/25, 8:09 PM

but the errors are happening on requests with cookies too

Aalex sorry, meant `( request.headers.get( 'cookie' ) || '' ).includes`*

C

Chaika•5/24/25, 8:24 PM

You can use the snippet editor to simulate some of the requests and look for errors, and you can always try/catch inside of your code and have a fallback, like fetching your origin anyway and throwing the error into a response header, or responding with the error, etc. Not great, but it's what there currently is

C

Chaika•5/24/25, 8:25 PM

even something silly like

    try {
      throw new Error("bleh")
    return fetch(request);
    }
    catch (err) {
      var response =  await fetch(request);
      const modifiedResponse = new Response(response.body, response);
      modifiedResponse.headers.set("error", JSON.stringify({ message: err.message, name: err.name, stack: err.stack, ...err }))
      return modifiedResponse;
    }

    try {
      throw new Error("bleh")
    return fetch(request);
    }
    catch (err) {
      var response =  await fetch(request);
      const modifiedResponse = new Response(response.body, response);
      modifiedResponse.headers.set("error", JSON.stringify({ message: err.message, name: err.name, stack: err.stack, ...err }))
      return modifiedResponse;
    }

    try {
      throw new Error("bleh")
    return fetch(request);
    }
    catch (err) {
      var response =  await fetch(request);
      const modifiedResponse = new Response(response.body, response);
      modifiedResponse.headers.set("error", JSON.stringify({ message: err.message, name: err.name, stack: err.stack, ...err }))
      return modifiedResponse;
    }

    try {
      throw new Error("bleh")
    return fetch(request);
    }
    catch (err) {
      var response =  await fetch(request);
      const modifiedResponse = new Response(response.body, response);
      modifiedResponse.headers.set("error", JSON.stringify({ message: err.message, name: err.name, stack: err.stack, ...err }))
      return modifiedResponse;
    }

would at least give you the line number

:"Error: bleh\n at fetch (52624/snippet.js:6:13)\n

M

max•5/25/25, 8:01 AM

Hi everyone! I am trying to use Workers for a little project but require FFmpeg, but there doesn't seem to be a library that will run on the workers runtime. Does anyone have a work around? I also saw cloudflare containers is coming out the end of next month that would solve my problem. Is there a way to get early beta access?

Mmax Hi everyone! I am trying to use Workers for a little project but require FFmpeg,...

1

1984 Ford Laser•5/25/25, 8:13 AM

Answer to first is no, answer to second is wait basically

11984 Ford Laser Answer to first is no, answer to second is wait basically

M

max•5/25/25, 8:23 AM

Okay fair enough. Thanks

M

max•5/25/25, 8:23 AM

Does anyone know of any good FFmpeg APIs?

1

1984 Ford Laser•5/25/25, 8:27 AM

What are you looking to achieve exactly with ffmpeg?

M

max•5/25/25, 8:58 AM

Will be cutting segments out of audio files and then re-encoding them

1

1984 Ford Laser•5/25/25, 9:49 AM

If it's audio only I wonder if there's some other JavaScript library you can use for handling audio encoding?

Cchipi 🐈Hi devs, according to browser rendering's [Reuse Sessions docs](https://develope...

R

Rui Figueira•5/25/25, 11:13 AM

forget my previous reply. If you want to reuse a browser with playwright, you need to obtain it with

connect

connect

connect

connect. When closing a browser obtained that way, it will still keep the session available for additional

connect

connect

connect

connect calls.

Here is an example:

import { acquire, connect } from '@cloudflare/playwright';

export default {
  async fetch(request: Request, env: Env) {
    // ensures session is acquired and kept alive for 20 seconds
    const { sessionId } = await acquire(env.MYBROWSER, { keep_alive: 20_000 });
    const browser = await connect(env.MYBROWSER, sessionId);

    // use the browser normally

    // it closes this browser instance but keeps the session alive
    await browser.close();

    // another browser instance can connect to the same session
    const otherBrowser = await connect(env.MYBROWSER, sessionId);

    // use the other browser instance with the same session

    await otherBrowser.close();

    // session is automatically closed after 20 seconds of inactivity
  },
};

import { acquire, connect } from '@cloudflare/playwright';

export default {
  async fetch(request: Request, env: Env) {
    // ensures session is acquired and kept alive for 20 seconds
    const { sessionId } = await acquire(env.MYBROWSER, { keep_alive: 20_000 });
    const browser = await connect(env.MYBROWSER, sessionId);

    // use the browser normally

    // it closes this browser instance but keeps the session alive
    await browser.close();

    // another browser instance can connect to the same session
    const otherBrowser = await connect(env.MYBROWSER, sessionId);

    // use the other browser instance with the same session

    await otherBrowser.close();

    // session is automatically closed after 20 seconds of inactivity
  },
};

import { acquire, connect } from '@cloudflare/playwright';

export default {
  async fetch(request: Request, env: Env) {
    // ensures session is acquired and kept alive for 20 seconds
    const { sessionId } = await acquire(env.MYBROWSER, { keep_alive: 20_000 });
    const browser = await connect(env.MYBROWSER, sessionId);

    // use the browser normally

    // it closes this browser instance but keeps the session alive
    await browser.close();

    // another browser instance can connect to the same session
    const otherBrowser = await connect(env.MYBROWSER, sessionId);

    // use the other browser instance with the same session

    await otherBrowser.close();

    // session is automatically closed after 20 seconds of inactivity
  },
};

import { acquire, connect } from '@cloudflare/playwright';

export default {
  async fetch(request: Request, env: Env) {
    // ensures session is acquired and kept alive for 20 seconds
    const { sessionId } = await acquire(env.MYBROWSER, { keep_alive: 20_000 });
    const browser = await connect(env.MYBROWSER, sessionId);

    // use the browser normally

    // it closes this browser instance but keeps the session alive
    await browser.close();

    // another browser instance can connect to the same session
    const otherBrowser = await connect(env.MYBROWSER, sessionId);

    // use the other browser instance with the same session

    await otherBrowser.close();

    // session is automatically closed after 20 seconds of inactivity
  },
};

Mmax Hi everyone! I am trying to use Workers for a little project but require FFmpeg,...

R

Rui Figueira•5/25/25, 3:31 PM

you can try using https://github.com/ffmpegwasm/ffmpeg.wasm

GitHub

GitHub - ffmpegwasm/ffmpeg.wasm: FFmpeg for browser, powered by Web...

FFmpeg for browser, powered by WebAssembly. Contribute to ffmpegwasm/ffmpeg.wasm development by creating an account on GitHub.

R

Rui Figueira•5/25/25, 3:35 PM

what I did:

- Install the library (

npm i @ffmpeg/ffmpeg @ffmpeg/core

npm i @ffmpeg/ffmpeg @ffmpeg/core

npm i @ffmpeg/ffmpeg @ffmpeg/core

npm i @ffmpeg/ffmpeg @ffmpeg/core)
- Add the following example code (note: wasm import needs to point directly to the file under

node_modules

node_modules

)

// @ts-ignore
import createFFmpegCore from '@ffmpeg/core';
// @ts-ignore
import wasm from '../node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm';
import type { FFmpegCoreModule } from '@ffmpeg/types';

// for some reason, ffmpeg-core tries to access location.href...
(globalThis as any).location = { href: 'https://example.com' };
const mod = {
  instantiateWasm: async (info: any, receiveInstance: any) => {
    const instance = await WebAssembly.instantiate(wasm, info);
    receiveInstance(instance);
  }
};
const ffmpeg = await createFFmpegCore(mod) as FFmpegCoreModule;

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const videoFile = new URL(request.url).searchParams.get('video')
      ?? 'https://raw.githubusercontent.com/ffmpegwasm/testdata/master/Big_Buck_Bunny_180_10s.webm';

    const input = await fetch(videoFile);
    ffmpeg.FS.writeFile('input.mp4', await input.bytes());
    ffmpeg.exec('-i', 'input.mp4', '-vf', 'format=gray', 'output.mp4');

    const output = ffmpeg.FS.readFile('output.mp4', { encoding: 'binary' });

    ffmpeg.FS.unlink('input.mp4');
    ffmpeg.FS.unlink('output.mp4');

    return new Response(output, {
      headers: {
        'Content-Type': 'video/mp4',
      },
    });
  },
};

// @ts-ignore
import createFFmpegCore from '@ffmpeg/core';
// @ts-ignore
import wasm from '../node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm';
import type { FFmpegCoreModule } from '@ffmpeg/types';

// for some reason, ffmpeg-core tries to access location.href...
(globalThis as any).location = { href: 'https://example.com' };
const mod = {
  instantiateWasm: async (info: any, receiveInstance: any) => {
    const instance = await WebAssembly.instantiate(wasm, info);
    receiveInstance(instance);
  }
};
const ffmpeg = await createFFmpegCore(mod) as FFmpegCoreModule;

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const videoFile = new URL(request.url).searchParams.get('video')
      ?? 'https://raw.githubusercontent.com/ffmpegwasm/testdata/master/Big_Buck_Bunny_180_10s.webm';

    const input = await fetch(videoFile);
    ffmpeg.FS.writeFile('input.mp4', await input.bytes());
    ffmpeg.exec('-i', 'input.mp4', '-vf', 'format=gray', 'output.mp4');

    const output = ffmpeg.FS.readFile('output.mp4', { encoding: 'binary' });

    ffmpeg.FS.unlink('input.mp4');
    ffmpeg.FS.unlink('output.mp4');

    return new Response(output, {
      headers: {
        'Content-Type': 'video/mp4',
      },
    });
  },
};

// @ts-ignore
import createFFmpegCore from '@ffmpeg/core';
// @ts-ignore
import wasm from '../node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm';
import type { FFmpegCoreModule } from '@ffmpeg/types';

// for some reason, ffmpeg-core tries to access location.href...
(globalThis as any).location = { href: 'https://example.com' };
const mod = {
  instantiateWasm: async (info: any, receiveInstance: any) => {
    const instance = await WebAssembly.instantiate(wasm, info);
    receiveInstance(instance);
  }
};
const ffmpeg = await createFFmpegCore(mod) as FFmpegCoreModule;

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const videoFile = new URL(request.url).searchParams.get('video')
      ?? 'https://raw.githubusercontent.com/ffmpegwasm/testdata/master/Big_Buck_Bunny_180_10s.webm';

    const input = await fetch(videoFile);
    ffmpeg.FS.writeFile('input.mp4', await input.bytes());
    ffmpeg.exec('-i', 'input.mp4', '-vf', 'format=gray', 'output.mp4');

    const output = ffmpeg.FS.readFile('output.mp4', { encoding: 'binary' });

    ffmpeg.FS.unlink('input.mp4');
    ffmpeg.FS.unlink('output.mp4');

    return new Response(output, {
      headers: {
        'Content-Type': 'video/mp4',
      },
    });
  },
};

// @ts-ignore
import createFFmpegCore from '@ffmpeg/core';
// @ts-ignore
import wasm from '../node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm';
import type { FFmpegCoreModule } from '@ffmpeg/types';

// for some reason, ffmpeg-core tries to access location.href...
(globalThis as any).location = { href: 'https://example.com' };
const mod = {
  instantiateWasm: async (info: any, receiveInstance: any) => {
    const instance = await WebAssembly.instantiate(wasm, info);
    receiveInstance(instance);
  }
};
const ffmpeg = await createFFmpegCore(mod) as FFmpegCoreModule;

export default {
  async fetch(request: Request, env: Env, ctx: ExecutionContext): Promise<Response> {
    const videoFile = new URL(request.url).searchParams.get('video')
      ?? 'https://raw.githubusercontent.com/ffmpegwasm/testdata/master/Big_Buck_Bunny_180_10s.webm';

    const input = await fetch(videoFile);
    ffmpeg.FS.writeFile('input.mp4', await input.bytes());
    ffmpeg.exec('-i', 'input.mp4', '-vf', 'format=gray', 'output.mp4');

    const output = ffmpeg.FS.readFile('output.mp4', { encoding: 'binary' });

    ffmpeg.FS.unlink('input.mp4');
    ffmpeg.FS.unlink('output.mp4');

    return new Response(output, {
      headers: {
        'Content-Type': 'video/mp4',
      },
    });
  },
};

R

Rui Figueira•5/25/25, 3:35 PM

That will convert a video into black and white

T

thipperz•5/25/25, 4:48 PM

How can I track which routes are consuming the most of CPU execution time?

M

max•5/25/25, 5:19 PM

oh wow @Rui Figueira thats amazing thank you. I had tried using the ffmpeg.wasm but failed - I guess I just dismissed it too early

M

max•5/25/25, 5:20 PM

one issue I have is that packaging this worker up now is too big for me to deploy on the free plan, but I think might even be too big for the paid plan too, 30mg uncompressed, and just slightly over 10mg compressed

Mmax one issue I have is that packaging this worker up now is too big for me to deplo...

R

Rui Figueira•5/25/25, 5:33 PM

hmm, you're right, but I was able to deploy it with a free plan

M

max•5/25/25, 5:33 PM

really? that is weird? maybe I've installed something else

M

max•5/25/25, 5:34 PM

I was trying to see if I can load it from a bucket

Mmax I was trying to see if I can load it from a bucket

R

Rui Figueira•5/25/25, 5:38 PM

This is my output, but it is definitely above 3MB limit from free plan...

Total Upload: 31672.57 KiB / gzip: 10087.55 KiB
Worker Startup Time: 45 ms
No bindings found.
Uploaded ffmpeg-example (10.47 sec)
Deployed ffmpeg-example triggers (2.74 sec)

Total Upload: 31672.57 KiB / gzip: 10087.55 KiB
Worker Startup Time: 45 ms
No bindings found.
Uploaded ffmpeg-example (10.47 sec)
Deployed ffmpeg-example triggers (2.74 sec)

Total Upload: 31672.57 KiB / gzip: 10087.55 KiB
Worker Startup Time: 45 ms
No bindings found.
Uploaded ffmpeg-example (10.47 sec)
Deployed ffmpeg-example triggers (2.74 sec)

Total Upload: 31672.57 KiB / gzip: 10087.55 KiB
Worker Startup Time: 45 ms
No bindings found.
Uploaded ffmpeg-example (10.47 sec)
Deployed ffmpeg-example triggers (2.74 sec)

RRui Figueira This is my output, but it is definitely above 3MB limit from free plan... ``` T...

M

max•5/25/25, 6:21 PM

hmm thats strange, definitely the free plan?

S

Shizlie•5/25/25, 6:50 PM

hi, anyone who can get the worker's (beta) rate limit to work? I need your help

S

SuperHelpflare•5/25/25, 6:57 PM

https://dontasktoask.com/

Don't ask to ask, just ask

Mmax hmm thats strange, definitely the free plan?

R

Rui Figueira•5/25/25, 7:50 PM

Yes, free plan. Did you try to deploy and it failed?

RRui Figueira Yes, free plan. Did you try to deploy and it failed?

M

max•5/25/25, 7:55 PM

Yeah, it says it exceeds the file limit

M

max•5/25/25, 7:55 PM

⛅️ wrangler 4.16.1
-------------------

Total Upload: 31652.23 KiB / gzip: 10083.07 KiB
No bindings found.
▲ [WARNING] Here are the 3 largest dependencies included in your script:

  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm - 31476.97 KiB
  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.js - 173.98 KiB
  - src/index.ts - 1.01 KiB
  If these are unnecessary, consider removing them



✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/workers-test/versions) failed.

  Your Worker exceeded the size limit of 3 MiB. Please upgrade to a paid plan to
  deploy Workers up to 10 MiB.
  https://dash.cloudflare.com/.../workers/plans
  [code: 10027]
  To learn more about this error, visit:
  https://developers.cloudflare.com/workers/platform/limits/#worker-size

  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

⛅️ wrangler 4.16.1
-------------------

Total Upload: 31652.23 KiB / gzip: 10083.07 KiB
No bindings found.
▲ [WARNING] Here are the 3 largest dependencies included in your script:

  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm - 31476.97 KiB
  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.js - 173.98 KiB
  - src/index.ts - 1.01 KiB
  If these are unnecessary, consider removing them



✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/workers-test/versions) failed.

  Your Worker exceeded the size limit of 3 MiB. Please upgrade to a paid plan to
  deploy Workers up to 10 MiB.
  https://dash.cloudflare.com/.../workers/plans
  [code: 10027]
  To learn more about this error, visit:
  https://developers.cloudflare.com/workers/platform/limits/#worker-size

  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

⛅️ wrangler 4.16.1
-------------------

Total Upload: 31652.23 KiB / gzip: 10083.07 KiB
No bindings found.
▲ [WARNING] Here are the 3 largest dependencies included in your script:

  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm - 31476.97 KiB
  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.js - 173.98 KiB
  - src/index.ts - 1.01 KiB
  If these are unnecessary, consider removing them



✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/workers-test/versions) failed.

  Your Worker exceeded the size limit of 3 MiB. Please upgrade to a paid plan to
  deploy Workers up to 10 MiB.
  https://dash.cloudflare.com/.../workers/plans
  [code: 10027]
  To learn more about this error, visit:
  https://developers.cloudflare.com/workers/platform/limits/#worker-size

  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

⛅️ wrangler 4.16.1
-------------------

Total Upload: 31652.23 KiB / gzip: 10083.07 KiB
No bindings found.
▲ [WARNING] Here are the 3 largest dependencies included in your script:

  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.wasm - 31476.97 KiB
  - node_modules/@ffmpeg/core/dist/esm/ffmpeg-core.js - 173.98 KiB
  - src/index.ts - 1.01 KiB
  If these are unnecessary, consider removing them



✘ [ERROR] A request to the Cloudflare API (/accounts/.../workers/scripts/workers-test/versions) failed.

  Your Worker exceeded the size limit of 3 MiB. Please upgrade to a paid plan to
  deploy Workers up to 10 MiB.
  https://dash.cloudflare.com/.../workers/plans
  [code: 10027]
  To learn more about this error, visit:
  https://developers.cloudflare.com/workers/platform/limits/#worker-size

  
  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

M

max•5/25/25, 7:57 PM

I've been trying to dynamically download from r2 and compile the wasm module, but I don't think it's possible

Mmax I've been trying to dynamically download from r2 and compile the wasm module, bu...

R

Rui Figueira•5/25/25, 8:01 PM

I tried with a different account, I also hit the limit there

M

max•5/25/25, 8:02 PM

oh so you've just got a lucky account?...

Mmax oh so you've just got a lucky account?...

R

Rui Figueira•5/25/25, 8:03 PM

so it seems

B

bun•5/26/25, 10:25 AM

wth is going on?! why does deploying a static website need a worker now ?

B

bun•5/26/25, 12:21 PM

export default {
  fetch: async (
    request: Request,
    env: { JWT_SECRET: string }
  ): Promise<Response> => {
    const token = request.headers.get("authorization");

    if (!token) {
      return new Response("unauthorized", { status: 401 });
    }

    try {
      await validateJWT(token, env.JWT_SECRET);

      return new Response(null, {
        status: 404 // meant as success for cloudflare to serve assets
      });
    } catch {
      return new Response("forbidden", { status: 403 });
    }
  }
};

export default {
  fetch: async (
    request: Request,
    env: { JWT_SECRET: string }
  ): Promise<Response> => {
    const token = request.headers.get("authorization");

    if (!token) {
      return new Response("unauthorized", { status: 401 });
    }

    try {
      await validateJWT(token, env.JWT_SECRET);

      return new Response(null, {
        status: 404 // meant as success for cloudflare to serve assets
      });
    } catch {
      return new Response("forbidden", { status: 403 });
    }
  }
};

export default {
  fetch: async (
    request: Request,
    env: { JWT_SECRET: string }
  ): Promise<Response> => {
    const token = request.headers.get("authorization");

    if (!token) {
      return new Response("unauthorized", { status: 401 });
    }

    try {
      await validateJWT(token, env.JWT_SECRET);

      return new Response(null, {
        status: 404 // meant as success for cloudflare to serve assets
      });
    } catch {
      return new Response("forbidden", { status: 403 });
    }
  }
};

export default {
  fetch: async (
    request: Request,
    env: { JWT_SECRET: string }
  ): Promise<Response> => {
    const token = request.headers.get("authorization");

    if (!token) {
      return new Response("unauthorized", { status: 401 });
    }

    try {
      await validateJWT(token, env.JWT_SECRET);

      return new Response(null, {
        status: 404 // meant as success for cloudflare to serve assets
      });
    } catch {
      return new Response("forbidden", { status: 403 });
    }
  }
};

B

bun•5/26/25, 12:21 PM

any idea why does the following code not work :/ ?

B

bun•5/26/25, 12:22 PM

like for some reason the page loads fine, when it shouldn't without a valid token, but in debugger, the requests come as 401, meaning the validation only works inside the debugger?

Bbun any idea why does the following code not work :/ ?

C

Chaika•5/26/25, 12:40 PM

Two problems

By default, Your worker/user code isn't going to be called if the path exactly matches an asset, you'd have to add

run_worker_first = true

run_worker_first = true

run_worker_first = true

run_worker_first = true to your config
https://developers.cloudflare.com/workers/static-assets/#routing-behavior

You'd have to configure your assets configuration to have a binding (like

ASSETS

ASSETS

ASSETS

ASSETS) and then call through to it:

return env.ASSETS.fetch(request);

return env.ASSETS.fetch(request);

return env.ASSETS.fetch(request);

return env.ASSETS.fetch(request);

B

bun•5/26/25, 12:41 PM

Thank you, works perfectly

I

Isaac McFadyen•5/26/25, 1:06 PM

Note that if you run_worker_first then you will always be billed for asset requests (i.e. no free serving of assets like Pages)

IIsaac McFadyen Note that if you run_worker_first then you will always be billed for asset reque...

B

bun•5/26/25, 1:43 PM

do u think there's a way to serve assets while at the same time validate jwt header?

B

bun•5/26/25, 1:43 PM

without being on enterprise tier

Bbun do u think there's a way to serve assets while at the same time validate jwt hea...

I

Isaac McFadyen•5/26/25, 1:44 PM

Your method will work but you would be billed. You could use Snippets if you're on a non-Free plan.

D

dave•5/26/25, 1:52 PM

Was there a recent update on mTLS working for Worker-to-Worker? I thought there was a blog post or something about it.. but can't find anything now.

Bbun do u think there's a way to serve assets while at the same time validate jwt hea...

D

dave•5/26/25, 1:57 PM

If you want to avoid Workers and Snippets, you can use a HMAC (symmetric algorithm only).

https://developers.cloudflare.com/ruleset-engine/rules-language/functions/#hmac-validation

Personally I prefer Snippets a lot more, since you can use ES256 (ECDSA with the P256 curve + SHA256). Using an asymmetric algorithm is so much nicer, since you don't have to worry about the validator ever needing to know what the secret was.

Ddave If you want to avoid Workers and Snippets, you can use a HMAC (symmetric algorit...

C

Chaika•5/26/25, 2:02 PM

You'd then need Pro for HMAC, which has Snippets anyway lol

CChaika You'd then need Pro for HMAC, which has Snippets anyway lol

D

dave•5/26/25, 2:13 PM

ya, but in some cases one might be better than the other. IIRC the WAF doesn't run when you do requests from your own Workers in the same zone, right?

Ddave ya, but in some cases one might be better than the other. IIRC the WAF doesn't r...

C

Chaika•5/26/25, 2:14 PM

That's confused me before, I think you're right

There is now a compat flag which I believe should get around that:
https://developers.cloudflare.com/workers/configuration/compatibility-flags/#global-fetch-strictly-public
If you were running an untrusted worker

Cloudflare Docs

Compatibility flags

Opt into a specific features of the Workers runtime for your Workers project.

CChaika That's confused me before, I think you're right There is now a compat flag whic...

D

dave•5/26/25, 3:12 PM

woah, that's really cool! I wish there was a way to do that per request

D

dave•5/26/25, 3:27 PM

I guess I could do a service binding to a Worker (with global_fetch_strictly_public enabled) that exposes a fetch?

sorry, meant `( request.headers.get( 'cookie' ) || '' ).includes`*

Similar Threads

Similar Threads

Similar Threads