```ts await ctx.request.arrayBuffer() ```

HHello, I’m Allie!```ts await ctx.request.arrayBuffer() ```

N

Nima•4/25/24, 11:35 AM

const { request, env } = context;

const rawBody = await request.arrayBuffer()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.arrayBuffer()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.arrayBuffer()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.arrayBuffer()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

Err:

Webhook payload must be provided as a string or a Buffer (https://nodejs.org/api/buffer.html) instance representing the _raw_ request body.PPayload was provided as a parsed JavaScript object instead.
Signature verification is impossible without access to the original signed material.

Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

Webhook payload must be provided as a string or a Buffer (https://nodejs.org/api/buffer.html) instance representing the _raw_ request body.PPayload was provided as a parsed JavaScript object instead.
Signature verification is impossible without access to the original signed material.

Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

Webhook payload must be provided as a string or a Buffer (https://nodejs.org/api/buffer.html) instance representing the _raw_ request body.PPayload was provided as a parsed JavaScript object instead.
Signature verification is impossible without access to the original signed material.

Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

Webhook payload must be provided as a string or a Buffer (https://nodejs.org/api/buffer.html) instance representing the _raw_ request body.PPayload was provided as a parsed JavaScript object instead.
Signature verification is impossible without access to the original signed material.

Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

NNima ```js const { request, env } = context; const rawBody = await request.arrayBuff...

H

Hello, I’m Allie!OP•4/25/24, 11:38 AM

Oh, they want a

Buffer

Buffer

Buffer

Buffer, not an

ArrayBuffer

ArrayBuffer

ArrayBuffer

ArrayBuffer... How about

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

HHello, I’m Allie!Oh, they want a `Buffer`, not an `ArrayBuffer`... How about ```ts const { reques...

N

Nima•4/25/24, 11:40 AM

I tried that initially, but i get:

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const { request, env } = context;

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

const event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

Err:

No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.

No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.

No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.

No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.

N

Nima•4/25/24, 11:40 AM

Is it actually a header problem and not a rawBody problem?

NNima I tried that initially, but i get: ```js const { request, env } = context; cons...

_

_pear•4/25/24, 12:20 PM

I was dealing with the exact same issue yesterday. I updated my webhook secret and it started working so maybe try that?

__pear I was dealing with the exact same issue yesterday. I updated my webhook secret a...

N

Nima•4/25/24, 12:24 PM

I assume that is for when you boot up another instance of "./stripe.exe listen --forward-to", no? Cuz it gives a new key.

When the stripe developers log their rawbody using express on nodejs instead, they get:
<Buffer 7b 0a 20 20 22 69 64 22 3a 20 22 65 76 74 ... 2344 more bytes>

But cloudflare worker functions does not have a way to get that from the request?

_

_pear•4/25/24, 12:26 PM

did you set the httpClient to a

Stripe.createHttpFetch()

Stripe.createHttpFetch()

Stripe.createHttpFetch()

Stripe.createHttpFetch() or whatever the method is? I'm not at my compooter rn but they show it in the blog post that announced stripe+workers

_

_pear•4/25/24, 12:26 PM

i think i had to make that change as well

_

_pear•4/25/24, 12:27 PM

Stripe(env.STRIPE_KEY, {
      httpClient: Stripe.createFetchHttpClient(), // ensure we use a Fetch client, and not Node's `http`
  });

Stripe(env.STRIPE_KEY, {
      httpClient: Stripe.createFetchHttpClient(), // ensure we use a Fetch client, and not Node's `http`
  });

Stripe(env.STRIPE_KEY, {
      httpClient: Stripe.createFetchHttpClient(), // ensure we use a Fetch client, and not Node's `http`
  });

Stripe(env.STRIPE_KEY, {
      httpClient: Stripe.createFetchHttpClient(), // ensure we use a Fetch client, and not Node's `http`
  });

_

_pear•4/25/24, 12:28 PM

i think that was part of my issue as well because it worked locally but not deployed

__pear i think that was part of my issue as well because it worked locally but not depl...

N

Nima•4/25/24, 12:31 PM

It is in local that it's not working for me.

So you set the stripe initilization to this (?):

const stripe = new Stripe(env.STRIPE_SECRET_KEY, { 
    apiVersion: '2023-10-16', 
    httpClient: Stripe.createFetchHttpClient()
  })

const stripe = new Stripe(env.STRIPE_SECRET_KEY, { 
    apiVersion: '2023-10-16', 
    httpClient: Stripe.createFetchHttpClient()
  })

const stripe = new Stripe(env.STRIPE_SECRET_KEY, { 
    apiVersion: '2023-10-16', 
    httpClient: Stripe.createFetchHttpClient()
  })

const stripe = new Stripe(env.STRIPE_SECRET_KEY, { 
    apiVersion: '2023-10-16', 
    httpClient: Stripe.createFetchHttpClient()
  })

And then run:

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

const rawBody = await request.text()
const stripeSignature = request.headers.get('stripe-signature')

event = await stripe.webhooks.constructEventAsync(rawBody, stripeSignature, env.STRIPE_WEBHOOK_SECRET)

NNima It is in local that it's not working for me. So you set the stripe initilizati...

N

Nima•4/25/24, 12:32 PM

⚠️  Webhook signature verification failed. Err: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.                             
                                                                                                                                                                                            
Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

⚠️  Webhook signature verification failed. Err: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.                             
                                                                                                                                                                                            
Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

⚠️  Webhook signature verification failed. Err: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.                             
                                                                                                                                                                                            
Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

⚠️  Webhook signature verification failed. Err: No signatures found matching the expected signature for payload. Are you passing the raw request body you received from Stripe?             ╮
 If a webhook request is being forwarded by a third-party tool, ensure that the exact request body, including JSON formatting and new line style, is preserved.                             
                                                                                                                                                                                            
Learn more about webhook signing and explore webhook integration examples for various frameworks at https://github.com/stripe/stripe-node#webhook-signing

NNima It is in local that it's not working for me. So you set the stripe initilizati...

_

_pear•4/25/24, 12:32 PM

are you using the stripe CLI locally to spin up the event forwarder and are you sending events via the CLI locally?

__pear are you using the stripe CLI locally to spin up the event forwarder and are you ...

N

Nima•4/25/24, 12:32 PM

Yup

NNima Yup

_

_pear•4/25/24, 12:32 PM

hmm and if you're using the correct secret for your local webhook it should work

N

Nima•4/25/24, 12:35 PM

Can it have to do with the API version then?

N

Nima•4/25/24, 12:36 PM

There came a new API version not that long ago, no (stripe)?

_

_pear•4/25/24, 12:36 PM

is there any middleware or something like that on the webook route that may be making changes to the request before it gets to the webhook?

maybe, i dont have that set but i think it's using the same version you have there.

__pear is there any middleware or something like that on the webook route that may be m...

N

Nima•4/25/24, 12:40 PM

All I am using in the application is, Vite + Nodejs. Which builds to a format that is compatible to run with Cloudflare pages. Other than importing the Stripe into the functions "import Stripe from 'stripe'" I am not using any other middleware.

__pear is there any middleware or something like that on the webook route that may be m...

N

Nima•4/25/24, 12:41 PM

The endpoint is in its own folder. And a singular file.

_

_pear•4/25/24, 12:44 PM

im out of ideas

it sounds like you have everything set up correctly. maybe the next step would be to get a minimal example repo. sometimes when i do that i realize that something is misconfigured or at least you'll have something to go along with a bug report to Stripe/Cloudflare

_

_pear•4/25/24, 12:45 PM

good luck!

I

IEatBeans•4/26/24, 3:14 AM

is it possible to generate sourcemaps for the pages functions? Im using sentry

I

IEatBeans•4/26/24, 3:15 AM

I am able to log the errors with the pages plugin, but there are no stack traces
https://developers.cloudflare.com/pages/functions/plugins/sentry/

Jjs Hey did you ever determine the best solution for this?

S

Snorre•4/26/24, 10:26 AM

I did not. :/

__pear im out of ideas 😦 it sounds like you have everything set up correctly. maybe th...

N

Nima•4/26/24, 10:34 AM

Is this the article you were referring to?
https://blog.cloudflare.com/announcing-stripe-support-in-workers

It's 3 years old, though. Thanks for the ideas nonetheless. I appreciate it a lot.

In the example provided, it passes in some additional values, it seems:

const stripe = getStripe({ env })
const body = await request.text()
const sig = request.headers.get('stripe-signature')
const webCrypto = Stripe.createSubtleCryptoProvider()
    
const event = await stripe.webhooks.constructEventAsync(
      body
      sig,
      env.STRIPE_ENDPOINT_SECRET,
      undefined,
      webCrypto
    )

const stripe = getStripe({ env })
const body = await request.text()
const sig = request.headers.get('stripe-signature')
const webCrypto = Stripe.createSubtleCryptoProvider()
    
const event = await stripe.webhooks.constructEventAsync(
      body
      sig,
      env.STRIPE_ENDPOINT_SECRET,
      undefined,
      webCrypto
    )

const stripe = getStripe({ env })
const body = await request.text()
const sig = request.headers.get('stripe-signature')
const webCrypto = Stripe.createSubtleCryptoProvider()
    
const event = await stripe.webhooks.constructEventAsync(
      body
      sig,
      env.STRIPE_ENDPOINT_SECRET,
      undefined,
      webCrypto
    )

const stripe = getStripe({ env })
const body = await request.text()
const sig = request.headers.get('stripe-signature')
const webCrypto = Stripe.createSubtleCryptoProvider()
    
const event = await stripe.webhooks.constructEventAsync(
      body
      sig,
      env.STRIPE_ENDPOINT_SECRET,
      undefined,
      webCrypto
    )

The Cloudflare Blog

Announcing native support for Stripe’s JavaScript SDK in Cloudflare...

Handling payments inside your apps is crucial to building a business online. For many developers, the leading choice for handling payments is Stripe.

_

_pear•4/26/24, 9:55 PM

yeah that's the article. i used the same setup and things are working.

X

x_m_e_x•4/27/24, 10:10 PM

Hey all! I need help to cache my backend apis that i cache in cloudfront before. How to move api cachings to cloudflare? Please help!!

O

oun.abbas•4/28/24, 9:48 PM

Hi all, I have an angular app, I want to use page plugin with it. I have created function dir and also included it in dist. is there any example of using page function with angular ?

P

Paolo•4/29/24, 10:41 AM

can you suggest a linter that works well with Functions? I'm a bit concerned about not catching Rejects

Z

zwily•4/30/24, 4:56 PM

Re-posting this from the discussions channel where I posted a week ago... Does anyone know how to reference a local DO from a local Pages app after the change in 3.46 (named endpoints)? See: pages-discussions

E

earwaf•5/2/24, 3:29 AM

This just started happening today, does anyone know a fix for this error while building cf pages + functions:

The package "crypto" wasn't found on the file system but is built into node

The package "crypto" wasn't found on the file system but is built into node

The package "crypto" wasn't found on the file system but is built into node

The package "crypto" wasn't found on the file system but is built into node (also happens with fs and path)

I don't use these directly, it seems to be some kind of dependency which I haven't even updated today that is causing it so i'm not sure how to fix it with the node: prefix

Currently unable to deploy with this error

E

earwaf•5/2/24, 4:47 AM

Note that the master branch works fine but preview branches do not

M

Mike Nomitch•5/3/24, 4:02 PM

Hi all

. I'm having trouble getting a hello world with functions working locally or when deployed. Hoping I can get some guidance here.

I used a Solid JS starter project from here (https://developers.cloudflare.com/pages/framework-guides/deploy-a-solid-site/) and then added a

/functions/hello.js

/functions/hello.js

/functions/hello.js

/functions/hello.js file in the root of the project that looks like this:

export function onRequest(context) {
  return new Response("Hello, world!");
}

export function onRequest(context) {
  return new Response("Hello, world!");
}

export function onRequest(context) {
  return new Response("Hello, world!");
}

export function onRequest(context) {
  return new Response("Hello, world!");
}

I expected that if I ran

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev

npx wrangler pages dev and then went to

http://localhost:8788/hello

http://localhost:8788/hello

http://localhost:8788/hello

http://localhost:8788/hello I would just see "Hello, world!" but instead of that I see the 404 page of my frontend app.

I've also deployed to prod and see the same thing at "/hello". In the CF UI in the functions tab I see this in the routing config:

{
  "baseURL": "/",
  "routes": [
    {
      "method": "",
      "module": [
        "hello.js:onRequest"
      ],
      "mountPath": "/",
      "routePath": "/hello"
    }
  ]
}

{
  "baseURL": "/",
  "routes": [
    {
      "method": "",
      "module": [
        "hello.js:onRequest"
      ],
      "mountPath": "/",
      "routePath": "/hello"
    }
  ]
}

{
  "baseURL": "/",
  "routes": [
    {
      "method": "",
      "module": [
        "hello.js:onRequest"
      ],
      "mountPath": "/",
      "routePath": "/hello"
    }
  ]
}

{
  "baseURL": "/",
  "routes": [
    {
      "method": "",
      "module": [
        "hello.js:onRequest"
      ],
      "mountPath": "/",
      "routePath": "/hello"
    }
  ]
}

and locally

wrangler pages functions build

wrangler pages functions build

wrangler pages functions build

wrangler pages functions build works fine.

Any ideas? I'm thinking its some small basic bit of config I'm missing or maybe a misunderstanding of what a Hello World looks like?

MMike Nomitch Hi all 👋🏻. I'm having trouble getting a hello world with functions working loc...

H

Hello, I’m Allie!OP•5/3/24, 4:43 PM

Looking at the linked tutorial, it appears that Solid uses SSR. If that is the case, then you need to create that route through whatever mechanism solid provides, rather than the

/functions

/functions

/functions

/functions folder

H

Hello, I’m Allie!OP•5/3/24, 4:44 PM

I believe it is this: https://start.solidjs.com/core-concepts/api-routes

SolidStart Release Candidate Documentation

Early release documentation and resources for SolidStart Release Candidate

I

IEatBeans•5/6/24, 3:10 AM

I am using the mailchannels integration (via their rest api), and randomly (about 1 out of 5 emails) fails with this error "{"errors":["Failed to send email: EOF"]}". I cant find any info on this and don't know whats wrong. I can just send the exact same email html to the exact same destinations and it will fail sometimes. Thoughts?

M

master_Em•5/7/24, 4:06 PM

Hey everyone. I just created a function for my Pages project (Nuxt 3 website). I followed the tutorial in creating a simple function that returns a hello world response. But every time I hit the endpoint, I get a 404. Help, please.

P

Paolo•5/7/24, 7:27 PM

Heya! How isolated are separate requests? If I create a singleton in node.js it will create a single instance accessible by all requests, but I'm not sure about functions

PPaolo Heya! How isolated are separate requests? If I create a singleton in node.js it ...

H

Hello, I’m Allie!OP•5/7/24, 7:34 PM

There are no guarantees about isolation between requests. Generally, the isolate is only reused by a single browser/client, so putting stuff in the global scope won't save you much

HHello, I’m Allie!There are no guarantees about isolation between requests. Generally, the isolate...

P

Paolo•5/7/24, 7:36 PM

Thank you. The issue is I'm trying to set up a session object in the Middleware, but so far attempts to do that and be able to recover it in the functions has proved... Not reliable?

P

Paolo•5/7/24, 7:38 PM

I tried adding fields to context but they do not seem to carry up the Middleware > Middleware > function tree

PPaolo I tried adding fields to context but they do not seem to carry up the Middleware...

H

Hello, I’m Allie!OP•5/7/24, 7:38 PM

Do you have a repro?

HHello, I’m Allie!Do you have a repro?

P

Paolo•5/7/24, 7:39 PM

See that's confusing because I thought I had it working and this morning it did not

HHello, I’m Allie!Do you have a repro?