Is it possible to detect whether a request came from a service binding? This could potentially simpl

IItsWendell Is it possible to detect whether a request came from a service binding? This cou...

H

You can add your own data to

req.cf

req.cf

, then detect that.

HHello, I’m Allie!You can add your own data to `req.cf`, then detect that.

I

ItsWendellOP•9/17/23, 2:23 PM

I just tried this but looks like it doesn't seem to get passed (at least locally with wrangler)

, e.g.:

await ctx.env.IMAGE_SERVICE.fetch(
    "https://image-service.worker/v1/avatars/test",
    {
      cf: {
        // Both properties not in the request cf output in the image service worker.
        serviceBinding: "api-service",
        isInternal: true,
      },
      headers: {
        // Does show up in 
        "api-key": ctx.env.IMAGE_SERVICE_API_KEY
      },
    },
  );

await ctx.env.IMAGE_SERVICE.fetch(
    "https://image-service.worker/v1/avatars/test",
    {
      cf: {
        // Both properties not in the request cf output in the image service worker.
        serviceBinding: "api-service",
        isInternal: true,
      },
      headers: {
        // Does show up in 
        "api-key": ctx.env.IMAGE_SERVICE_API_KEY
      },
    },
  );

await ctx.env.IMAGE_SERVICE.fetch(
    "https://image-service.worker/v1/avatars/test",
    {
      cf: {
        // Both properties not in the request cf output in the image service worker.
        serviceBinding: "api-service",
        isInternal: true,
      },
      headers: {
        // Does show up in 
        "api-key": ctx.env.IMAGE_SERVICE_API_KEY
      },
    },
  );

await ctx.env.IMAGE_SERVICE.fetch(
    "https://image-service.worker/v1/avatars/test",
    {
      cf: {
        // Both properties not in the request cf output in the image service worker.
        serviceBinding: "api-service",
        isInternal: true,
      },
      headers: {
        // Does show up in 
        "api-key": ctx.env.IMAGE_SERVICE_API_KEY
      },
    },
  );

IItsWendell I just tried this but looks like it doesn't seem to get passed (at least locally...

H

Hello, I’m Allie!•9/17/23, 2:46 PM

Uh, I'm not 100% sure whether to classify that as a bug, since technically this is an undocumented feature...

S

sathoro•9/17/23, 3:53 PM

I had no idea about this "feature"

B

Ben-xD•9/17/23, 6:27 PM

Does wrangler3 support breakpoint debugging yet?

B

Brandon | Cloudflare TSE•9/17/23, 8:26 PM

hey all.

B

Brandon | Cloudflare TSE•9/17/23, 8:27 PM

I'm trying to test something for a customer with Workers, but I don't know anything about Javascript except how to read the English words that are in it.

Does anyone have in their notes, or can write for me real quick, a "K.I.S.S.", dirt simple .js to display an HTTP response with a connecting IP?

BBrandon | Cloudflare TSE I'm trying to test something for a customer with Workers, but I don't know anyth...

I

Isaac McFadyen•9/17/23, 8:32 PM

Sure!

export default {
  fetch(req) {
    const connectingIp = req.headers.get("cf-connecting-ip");
    return new Response("Connecting from: " + connectingIp, {
      headers: {
        "Content-Type": "text/plain"
      }
    });
  }
}

export default {
  fetch(req) {
    const connectingIp = req.headers.get("cf-connecting-ip");
    return new Response("Connecting from: " + connectingIp, {
      headers: {
        "Content-Type": "text/plain"
      }
    });
  }
}

export default {
  fetch(req) {
    const connectingIp = req.headers.get("cf-connecting-ip");
    return new Response("Connecting from: " + connectingIp, {
      headers: {
        "Content-Type": "text/plain"
      }
    });
  }
}

export default {
  fetch(req) {
    const connectingIp = req.headers.get("cf-connecting-ip");
    return new Response("Connecting from: " + connectingIp, {
      headers: {
        "Content-Type": "text/plain"
      }
    });
  }
}

B

Brandon | Cloudflare TSE•9/17/23, 8:34 PM

@Isaac McFadyen | YYZ01 Fantastic, thank you!

I was looking through our Examples page but I couldn't seem to locate what I was looking for. I had a feeling it was something with headers, but the rest of the code wasn't making sense.

I

Isaac McFadyen•9/17/23, 8:35 PM

Excuse my terrible indentation, fixed

B

Brandon | Cloudflare TSE•9/17/23, 8:36 PM

Your terrible indentation was fine, it did the job; https://ping.cfbrandon.ninja

I

Isaac McFadyen•9/17/23, 8:37 PM

B

benthecarman•9/17/23, 11:26 PM

Is there an easy way / guide for connecting to a postgres database from the rust workers?

B

benthecarman•9/17/23, 11:31 PM

Ah maybe i can use this?
https://github.com/supabase-community/postgrest-rs

Bbenthecarman Ah maybe i can use this? https://github.com/supabase-community/postgrest-rs

I

Isaac McFadyen•9/17/23, 11:32 PM

That requires PostgREST which is a seperate program that sits alongside your Postgres database

I

Isaac McFadyen•9/17/23, 11:32 PM

Supabase has it included, otherwise you'd need to deploy it yourself

B

benthecarman•9/17/23, 11:32 PM

I am using neon, do you know how I can set that up?

Bbenthecarman I am using neon, do you know how I can set that up?

I

Isaac McFadyen•9/17/23, 11:33 PM

Neon doesn't have support for PostgREST built-in, you'd need to set it up on a VPS or similar yourself.

B

benthecarman•9/17/23, 11:34 PM

Dang, is there no easy way to talk to neon without using javascript?

Bbenthecarman Dang, is there no easy way to talk to neon without using javascript?

I

Isaac McFadyen•9/17/23, 11:34 PM

Not that I know of on Workers. The difficulty is that Workers uses a custom TCP socket implementation which means that drivers need to be specifically designed for it.

I

Isaac McFadyen•9/17/23, 11:35 PM

As far as I know only JavaScript (pg and postgres.js) drivers for Postgres have been modified to work so far.

B

benthecarman•9/17/23, 11:37 PM

Dang that's unfortunate

B

benthecarman•9/17/23, 11:43 PM

Filed this, hopefully someone picks it up!
https://github.com/cloudflare/workers-rs/issues/386

GitHub

[Feature] PostgreSQL Support · Issue #386 · cloudflare/workers-rs

Is there an existing issue for this? I have searched the existing issues Description Recently you guys have announced support for various database integrations https://blog.cloudflare.com/announcin...

B

benthecarman•9/18/23, 12:07 AM

Oh wait just found this https://github.com/cloudflare/workers-rs/blob/main/examples/tokio-postgres/src/lib.rs

GitHub

workers-rs/examples/tokio-postgres/src/lib.rs at main · cloudflare/...

Write Cloudflare Workers in 100% Rust via WebAssembly - cloudflare/workers-rs

R

Rich•9/18/23, 2:36 AM

Does anybody know if it's safe to put

context.waitUntil

context.waitUntil

on the global to improve it's ergonomics or does it need to be coupled with a specific request? e.g.

// worker.js
import { myFetch } from './my-fetch';

export default {
  async fetch(request, env, context) {
    global.waitUntil = context.waitUntil;
    return fetch(request);
  },
};

// my-fetch.js
export const fetch = async (request) => {
  const response = await fetch(request); 
  response.headers.append("Cache-Control", "s-maxage=10");
  waitUntil(caches.default.put(request, response.clone()));
  return response;
}

// worker.js
import { myFetch } from './my-fetch';

export default {
  async fetch(request, env, context) {
    global.waitUntil = context.waitUntil;
    return fetch(request);
  },
};

// my-fetch.js
export const fetch = async (request) => {
  const response = await fetch(request); 
  response.headers.append("Cache-Control", "s-maxage=10");
  waitUntil(caches.default.put(request, response.clone()));
  return response;
}

// worker.js
import { myFetch } from './my-fetch';

export default {
  async fetch(request, env, context) {
    global.waitUntil = context.waitUntil;
    return fetch(request);
  },
};

// my-fetch.js
export const fetch = async (request) => {
  const response = await fetch(request); 
  response.headers.append("Cache-Control", "s-maxage=10");
  waitUntil(caches.default.put(request, response.clone()));
  return response;
}

// worker.js
import { myFetch } from './my-fetch';

export default {
  async fetch(request, env, context) {
    global.waitUntil = context.waitUntil;
    return fetch(request);
  },
};

// my-fetch.js
export const fetch = async (request) => {
  const response = await fetch(request); 
  response.headers.append("Cache-Control", "s-maxage=10");
  waitUntil(caches.default.put(request, response.clone()));
  return response;
}

JJames After their platform got hit with security issues. I would recommend avoiding Ma...

A

addison•9/18/23, 3:29 AM

is this not fixed now with the requirement for domain lockdown if using workers?

Aaddison is this not fixed now with the requirement for domain lockdown if using workers?

S

sathoro•9/18/23, 4:21 AM

if you care about deliverability and security I would use a service that does any level of manual domain verification which would be... all of them except Mailchannels. personally I recommend Postmark

Ssathoro if you care about deliverability and security I would use a service that does an...

A

addison•9/18/23, 4:23 AM

well don't you need to manually set a txt record on your domain now? so far I haven't seen any deliverability issues on my domains using mailchannels and they can't be triggered by another worker

Aaddison well don't you need to manually set a txt record on your domain now? so far I ha...

S

sathoro•9/18/23, 4:24 AM

I mean manual verification by a human, not automatic verification through a DNS record

S

sathoro•9/18/23, 4:25 AM

that's great, then continue using Mailchannels. I choose not to support companies who fail at core functionality and have had glaring security issues for years.

A

addison•9/18/23, 4:27 AM

to be fair I think there's a failure on multiple levels on most parties involved but yeah I can see why you would choose not to use mailchannels. I just like not having to pay to send emails which mailchannels is doing just fine for what I use it for and hopefully will continue doing so in the future.

RRich Does anybody know if it's safe to put `context.waitUntil` on the global to impro...

H

Hello, I’m Allie!•9/18/23, 7:20 AM

IIRC it is tied to the request

HHello, I’m Allie!IIRC it is tied to the request

R

Rich•9/18/23, 7:28 AM

Aww, that's a shame. I'm finding it causes me to have to pass

ctx

ctx

or

waitUntil

waitUntil

/

env

env

into various modules, creating a lot of boilerplate for call sites

RRich Aww, that's a shame. I'm finding it causes me to have to pass `ctx` or `waitUnti...

H

Hello, I’m Allie!•9/18/23, 7:39 AM

You can use

AsyncLocalStorage

AsyncLocalStorage

to pass request-bound variables around "globally".

AsyncLocalStorage · Cloudflare Workers docs

Cloudflare Workers provides an implementation of a subset of the Node.js AsyncLocalStorage API for creating in-memory stores that remain coherent …

HHello, I’m Allie!You can use [`AsyncLocalStorage`](https://developers.cloudflare.com/workers/runt...

R

Rich•9/18/23, 7:43 AM

Interesting, I'll take a look thanks

A

alotabits•9/18/23, 12:44 PM

How is cache.put coordinated when two concurrent requests in the same worker attempt to update the cache for the same cache key? Specifically in the case when both requests only .put after a .match failed. I’m assuming since there is no mutex or other lock mechanism that it’s basically “last request wins”.

S

simpson•9/18/23, 12:47 PM

We are looking to move all of our serverless functions to Cloudflare workers, one of the things we are trying to understand is how to best structure our project. Originally we wanted to have a single Worker, but with our 20-30 functions they each need their own different CRON schedules, so it seems like we'll have to make every function its own worker. However, there is a lot of shared logic between all these functions that i'd hate to duplicate many times over and have to try and manage that. Is there any best practices on how to build a large set of workers that can share libs and also have CRON flexibility?

Ssimpson We are looking to move all of our serverless functions to Cloudflare workers, on...

A

alotabits•9/18/23, 12:47 PM

Service bindings?

Ssimpson We are looking to move all of our serverless functions to Cloudflare workers, on...

S

sathoro•9/18/23, 12:48 PM

you could do a single worker and instead of using crons you could use durable object alarms

Aalotabits How is cache.put coordinated when two concurrent requests in the same worker att...

S

sathoro•9/18/23, 12:49 PM

probably yes

S

sathoro•9/18/23, 12:49 PM

the cache is per colo btw

Ssathoro you could do a single worker and instead of using crons you could use durable ob...

S

simpson•9/18/23, 12:59 PM

interesting! so bind a single worker to a DO and put all the scheduling logic there?

Ssimpson interesting! so bind a single worker to a DO and put all the scheduling logic th...

S

sathoro•9/18/23, 1:00 PM

sort of, but in your case you might want multiple DOs for each cron to simplify the scheduling. although I've also seen a library that would help with this (can't find it...)

Ssimpson interesting! so bind a single worker to a DO and put all the scheduling logic th...

S

sathoro•9/18/23, 1:05 PM

can make your own scheduler with a single DO (but multiple instances) like this using

itty-durable

itty-durable

itty-durable

itty-durable

import { createDurable } from "itty-durable";

export class Scheduler extends createDurable({ autoPersist: true }) {
  constructor(state, env) {
    super(state, env);
  }

  create(name, doEverySeconds = 30) {
    this.name = name;
    this.doEverySeconds = doEverySeconds;

    this.setAlarm(Date.now());
  }

  async alarm() {
    console.log(`Doing ${this.name}...`);

    this.setAlarm(Date.now() + this.doEverySeconds * 1000);

    // do the thing...
  }
}

import { createDurable } from "itty-durable";

export class Scheduler extends createDurable({ autoPersist: true }) {
  constructor(state, env) {
    super(state, env);
  }

  create(name, doEverySeconds = 30) {
    this.name = name;
    this.doEverySeconds = doEverySeconds;

    this.setAlarm(Date.now());
  }

  async alarm() {
    console.log(`Doing ${this.name}...`);

    this.setAlarm(Date.now() + this.doEverySeconds * 1000);

    // do the thing...
  }
}

import { createDurable } from "itty-durable";

export class Scheduler extends createDurable({ autoPersist: true }) {
  constructor(state, env) {
    super(state, env);
  }

  create(name, doEverySeconds = 30) {
    this.name = name;
    this.doEverySeconds = doEverySeconds;

    this.setAlarm(Date.now());
  }

  async alarm() {
    console.log(`Doing ${this.name}...`);

    this.setAlarm(Date.now() + this.doEverySeconds * 1000);

    // do the thing...
  }
}

import { createDurable } from "itty-durable";

export class Scheduler extends createDurable({ autoPersist: true }) {
  constructor(state, env) {
    super(state, env);
  }

  create(name, doEverySeconds = 30) {
    this.name = name;
    this.doEverySeconds = doEverySeconds;

    this.setAlarm(Date.now());
  }

  async alarm() {
    console.log(`Doing ${this.name}...`);

    this.setAlarm(Date.now() + this.doEverySeconds * 1000);

    // do the thing...
  }
}

S

sathoro•9/18/23, 1:05 PM

and the DO can import whatever code it needs to from your codebase directly

S

sathoro•9/18/23, 1:06 PM

(

itty-durable

itty-durable

itty-durable

itty-durable is not needed, it just makes the code way shorter)

D

dave•9/18/23, 2:41 PM

Does

.fetch

.fetch

.fetch

.fetch on a Service Worker binding do anything with the

cache-control

cache-control

cache-control

cache-control header?

TTraffy Does worker supports mongoose or mongodb driver?

L

Legendarist•9/18/23, 4:35 PM

https://www.mongodb.com/developer/products/atlas/cloudflare-worker-rest-api/

Create a REST API with Cloudflare Workers and MongoDB Atlas | MongoDB

Learn how to create a serverless REST API using Cloudflare workers and MongoDB Atlas.

LLegendarist https://www.mongodb.com/developer/products/atlas/cloudflare-worker-rest-api/

I

Isaac McFadyen•9/18/23, 5:06 PM

That's Atlas only but yes.

I

Isaac McFadyen•9/18/23, 5:06 PM

(Atlas is their hosted service)

Is it possible to detect whether a request came from a service binding? This could potentially simpl

Similar Threads

Similar Threads

Similar Threads