As an example of what Workers+WASM can do, you can check out https://og-playground.vercel.app/. In g

As an example of what Workers+WASM can do, you can check out https://og-playground.vercel.app/. In general, CF won't provide direct CF metrics, but I would say, for light/moderate loads, go with Workers+WASM, for heavy+ loads, go with something like https://fly.io

Vercel OG Image Playground

Generate Open Graph images with Vercel’s Edge Function.

KKavatch My main concern is just that I might hit the 30 sec timeout limit (for HTTP requ...

Jadugar_Jaggu•3/3/23, 11:52 AM

I use a task that takes 10 to 12 minutes using a worker. I just do it once an hour using cron triggers and KV

JJadugar_Jaggu I use a task that takes 10 to 12 minutes using a worker. I just do it once an ho...

Hello, I’m Allie!OP•3/3/23, 11:54 AM

The issue is the CPU Time. AFAIK, you still only get 30 seconds of CPU with Cron Triggers.

Hello, I’m Allie!OP•3/3/23, 11:55 AM

NVM

HHello, I’m Allie!As an example of what Workers+WASM can do, you can check out https://og-playgrou...

Kavatch•3/3/23, 11:55 AM

I will have a look at these sites , thank you!

Hello, I’m Allie!OP•3/3/23, 11:55 AM

I read the wrong section

Jadugar_Jaggu•3/3/23, 11:55 AM

he is asking for http request timeout

Jadugar_Jaggu•3/3/23, 11:55 AM

not cpu

Hello, I’m Allie!OP•3/3/23, 11:55 AM

Yeah, misread, sorry!

JJadugar_Jaggu Use cron triggers (hourly setting) to increase time limit

Kavatch•3/3/23, 11:57 AM

In general a good Idea however since I want to encode "on demand" I probably can't use cron jobs since I want to do it every time a user calls an endpoint. Thanks though!

KKavatch In general a good Idea however since I want to encode "on demand" I probably can...

Jadugar_Jaggu•3/3/23, 12:01 PM

If you want to do it on demand you can give a try to Queue. Cause in it consumer worker also support waitUntil() like cron

I am not that sure but you can try it

Jadugar_Jaggu•3/3/23, 12:03 PM

Just need to set the value of Message batch size to 1

NNicolaas Hi guys, is there any way to use a worker to make sure that requests going to ou...

Hello, I’m Allie!OP•3/3/23, 12:44 PM

You can use a CF Tunnel for that? Then you don't need to open any ports either.

Hello, I’m Allie!OP•3/3/23, 12:44 PM

For extra security, you can verify an Access JWT too.

NNicolaas Hi guys, is there any way to use a worker to make sure that requests going to ou...

DaniFoldi•3/3/23, 1:10 PM

You can also check out the new mTLS binding?

kian•3/3/23, 1:30 PM

I don't see it thrown from the runtime - that looks like it's thrown by wasm-bindgen

kian•3/3/23, 1:31 PM

Unless it's just thrown by V8 itself, which would be odd

kian•3/3/23, 1:34 PM

kian•3/3/23, 1:34 PM

Yeah, that's wasm-bindgen

kian•3/3/23, 1:37 PM

wasm-bindgen isn't something that is included in workerd

kian•3/3/23, 1:38 PM

Are you using WASM in your Worker?

kian•3/3/23, 1:47 PM

Is the image that fails larger than the rest?

kian•3/3/23, 1:53 PM

I'd have a global variable of initializedinitialized and only init inside an if check

kian•3/3/23, 1:54 PM

import esbuild from "esbuild-wasm";
import wasm from "../node_modules/esbuild-wasm/esbuild.wasm";

let initialised = false;
globalThis.performance = Date;

export default {
    async fetch(): Promise<Response> {
        if (!initialised) {
            await esbuild.initialize({
                wasmModule: wasm,
                worker: false,
            });
            initialised = true;
        }
        return new Response("Hello World");
    },
};

import esbuild from "esbuild-wasm";
import wasm from "../node_modules/esbuild-wasm/esbuild.wasm";

let initialised = false;
globalThis.performance = Date;

export default {
    async fetch(): Promise<Response> {
        if (!initialised) {
            await esbuild.initialize({
                wasmModule: wasm,
                worker: false,
            });
            initialised = true;
        }
        return new Response("Hello World");
    },
};

Example from https://blog.interactions.rest/blog/esbuild-on-the-edge/

NNicolaas Hi guys, is there any way to use a worker to make sure that requests going to ou...

Kavatch•3/3/23, 2:00 PM

It sounds like what you want is something along the lines of this here: https://developers.cloudflare.com/ssl/origin-configuration/origin-ca/#4-required-for-some-add-cloudflare-origin-ca-root-certificates
With that you can edit the configuration on your server to validate the certificate from cloudflare before accepting the request and thus preventing anyone from sending request not though cloudflare.
For example in Nginx you would add something like this to the server configuration:

ssl_client_certificate /etc/ssl/certs/cloudflare-origin.pem;
ssl_verify_client on;

ssl_client_certificate /etc/ssl/certs/cloudflare-origin.pem;
ssl_verify_client on;

About all of this there is also this excellent blog post: https://blog.jfx.ac/securing-nginx-origin-with-cloudflare.html

jfx Blog

How to secure your nginx + Cloudflare configuration to stop any ori...

I decided to write this as although a lot of guides on the internet provide a solid configuration for an nginx server, most of these guides will result in an IP leak somewhere under their configuration for the origin server somewhere. So you got your nginx server setup (hopefully) and it’s serving your files (or being an effective reverse proxy)...

Origin CA certificates · Cloudflare SSL/TLS docs

Use Origin Certificate Authority (CA) certificates to encrypt traffic between Cloudflare and your origin web server and reduce origin bandwidth …

kian•3/3/23, 2:05 PM

Bleh, might not work with svg2png then.

danielsundq•3/3/23, 2:19 PM

I experience some problems with cron triggers. The worker is unable to make a request to a non standard http port to a external service on the same domain (no-proxy DNS). Getting 404 if the worker is triggered with a cron event. It do work though if I trigger the same worker with a fetch request instead.

danielsundq•3/3/23, 2:19 PM

I then created a port proxy worker that proxies between the non standard http port and 443 in the same zone. As a result the reverse is true: the cron trigger works but not the worker triggered by an fetch event! I assume the fetch worker can't communicate with the port proxy directly because it's in the same zone. But it seems the cron triggered worker i able.

danielsundq•3/3/23, 2:26 PM

So it seems like the cron triggered worker is running in another zone

kian•3/3/23, 6:57 PM

I don't really know why that warning is there

kian•3/3/23, 6:57 PM

They're GA - https://blog.cloudflare.com/service-bindings-ga/

The Cloudflare Blog

Service Bindings are generally available, with efficient pricing

Service bindings are an API that facilitate Worker-to-Worker communication. You can invoke other Workers directly from your code; making it possible to communicate with shared services. We’ll also make it cost-efficient to run multiple Workers

import esbuild from "esbuild-wasm"; import wasm from "../node_modules/esbuild-wasm/esbuild.wasm"; let initialised = false; globalThis.performance = Date; export default { async fetch(): Promise<Response> { if (!initialised) { await esbuild.initialize({ wasmModule: wasm, worker: false, }); initialised = true; } return new Response("Hello World"); }, };

As an example of what Workers+WASM can do, you can check out https://og-playground.vercel.app/. In g

Similar Threads

Similar Threads

Similar Threads