My First Cloudflare Edge Worker | danisaacs.net: the blog

Open Table of contents

Intro
Initial implementation
Moving it to the edge
- Create (and customize) a new Worker
- Enable that Worker on a site
Example Edge Worker
Results
Resources

Intro

I’ve been working here for a long time, as a result I get asked for help with a lot of random stuff. Because of that, I end up touching a variety of technologies. (And very occasionally there’s even acknowledgement and/or recognition for those types of tasks.)

This time, I was asked to help support some of our experimentation team with their demo process — mainly, the ability for multiple users to leverage the same website with their own web experimentation javascript snippet.

Initial implementation

The initial implementation of this was some (very ugly) javascript I added to my site. It would:

Check for a specific URL query string, defining the web experimentation project ID
If that query string existed, take the project ID value and assign it to a cookie
Check if that cookie existed — if it does, take that project ID and use it to create the link to the experimentation snippet
Add the <script> tags to load the snippet to the site’s <head>.

Result? On a shared website instance, team members could include their experimentation project ID in the URL, and have their own exp snippet loaded on the site. Success! Kinda.

Moving it to the edge

Kinda? Well, did the original implementation work? Sure. But it was very slow, and led to flashing because the script was getting loaded so late in the process. The new idea? Add that script at the edge, before the page is loaded.

Most of our demo sites are already leveraging Cloudflare, and they offer a certain number of edge worker calls even on a free instance.

I’d never worked with them before — could an edge worker be leveraged to improve this process? Turns out yes, and it was pretty straightforward to figure out.

Create (and customize) a new Worker

So, how did I set this up? I’ll walk through what I did for this first Worker — more experienced users may (likely) do things differently, but I think this is a good starting place.

Most importantly: you obviously need a Cloudflare account, with your website traffic passing through it. If you don’t have that, this writeup isn’t going to be very helpful to you.

First, log in to your Cloudflare account. Then on the left side, in the “Workers & Pages” section, select “Overview”, and then “Create application”:

Getting started

That will bring you to this screen, where you can create a simple “Hello World” Worker — we’ll use this as a starting point:

Create a worker

Next you’ll see the sample “Hello World” code, and a name automatically assigned to your new Worker. You can update the name to align with your project, but we won’t edit the code until the next step. For now, just update the name (if you want), and click the “Deploy” button.

Create a worker

That will deploy the Worker, and bring you to a “congratulations” message — from here, we can click the “Edit code” button to go edit that code:

Create a worker

Now you’re in Cloudflare’s online code editor — time to update that javascript and make that code do what you want. I’ve included my sample Worker a few sections down in this post.

Enable that Worker on a site

Once you’re got your Worker set up, you’ll want to enable it on a site. In Cloudflare, click in to manage your domain. Then in the left menu, select “Workers Routes”.

From there, you can define where that new Worker should run — your entire website? Just a section? Whatever you want.

Assign a worker

Example Edge Worker

Here’s a very simple example of edge worker — it’s a simplified version of the Worker I’ve set up based on the requirements detailed above.

In this case, very briefly: it’s checking for a query string “pid”. If that query string exists, then it will automatically add the web experimentation snippet to top of the page’s <head> section; if not, it returns the page as-is. This is using an Element Handler in Cloudflare’s HTMLRewriter feature — a feature you’ll want to get to know — to add the element.

export default {
  async fetch(request) {
    const { searchParams } = new URL(request.url);
    let projId = searchParams.get("pid");

    class ElementHandler {
      constructor(pidValue) {
        this.pidValue = pidValue;
      }
      element(element) {
        element.prepend(
          `\n    <script src=\"https://cdn.optimizely.com/js/${this.pidValue}.js\"></script>`,
          { html: true }
        );
      }
    }

    const resp = await fetch(request);

    if (projId != null) {
      const rewriter = new HTMLRewriter().on(
        "head",
        new ElementHandler(projId)
      );
      return rewriter.transform(resp);
    } else {
      return resp;
    }
  },
};

Results

The edge worker was a success, and the experimentation snippet now loads much more quickly, and without flashing. And, I’ve added a new tool to my toolkit. My advice? If you’re thinking about getting started with Cloudflare Edge Workers — go for it.

Resources

Some resources I found helpful: