Try putting your assets in a subdirectory

HHello, I’m Allie!Try putting your assets in a subdirectory

B

Brutal Strike•4/22/24, 10:02 AM

like this? I still have: No webpage was found for the web address: https://5538651d.test2-55l.pages.dev/hello

Z

zegevlier•4/22/24, 10:05 AM

Put the

functions

functions

folder in the

test

test

folder, then upload the

public

public

folder.

B

Brutal Strike•4/22/24, 10:08 AM

thank you now its working

P

Paolo•4/22/24, 10:42 AM

I'm trying the Vitest testing tutorial for Functions but I get the following error "Using service bindings to the current worker requires

poolOptions.workers.main

poolOptions.workers.main

to be set to your worker's entrypoint". But I do not have an entrypoint :/

Zzegevlier Put the `functions` folder in the `test` folder, then upload the `public` folder...

M

Marius Gundersen•4/22/24, 5:32 PM

The way to structure the project isn't terribly clear from the documentation. It's not easy to understand from the words alone that functions should not be in public and where to put all the other special files (_redirects, _routes.json). I wish the documentation had a clear example of where these files should be

K

King•4/22/24, 11:57 PM

Hello everyone, Is it possible to send emails with attachments using the mailchannels plugin? Or has this feature not been implemented?

P

Paolo•4/23/24, 8:49 AM

has anyone gotten vitest working with functions like it's done with workers?

SSnorre Hello everyone. What would be the best way to co-ordinate refresh and access tok...

J

js•4/24/24, 12:50 AM

Hey did you ever determine the best solution for this?

T

tozz•4/24/24, 7:00 AM

Anyone else noticed that if you have a

onRequest

onRequest

function defined, other specific functions like

onRequestOptions

onRequestOptions

no longer gets called in the middleware? Seems like a regression since it used to work and I don't see anything about it changing in the release notes

D

danboyle8637•4/24/24, 1:47 PM

For some reason... it appears my service bindings are set up incorrectly but I can't figure out why.

I have a binding from a "normal" Worker to my Pages Worker. It's setup correctly in the dashboard (I am not using the wrangler.toml file in Pages yet).

In my particular case, I create a new Request object where the url is the path that matches a route in my destination Worker.

However, I always get an error stating that fetch can't call the url path I supply.

Just to be clear... I call my Request using

env.WORKER_BINDING_NAME.fetch(Request)

env.WORKER_BINDING_NAME.fetch(Request)

-- this call is made in a Pages function endpoint and I await it because I want the response.

The last wrinkle is I am testing in my staging environment. And in my CF Dashboard I bind to the correct Worker... BUT... there is a drop down when binding Workers for

environment

environment

and (for me at least) the only option I ever have it

production

production

.

So my Binding is made to my staging Worker... but the Dashboard binding drop down only ever gives

production

production

as an option.

I plan on switching to

wrangler.toml

wrangler.toml

config rather than Dashboard. It seems easier to manage for sure.

Any ideas on why it appears my Service Bindings aren't working?

A

Alek•4/24/24, 3:52 PM

It seems like I always get a MISS for the same URL I want to cache. Is it something I'm missing? "try {
let url = await context.request.url;

let paramString = url.split('?')[1];

if (paramString.includes('ntt=') || paramString.includes('lpurl'))
{
const today = new Date();
const tomorrow = new Date(today.getFullYear(), today.getMonth(), today.getDate() + 1);
const seconds = Math.floor((tomorrow.getTime() + 18000000 - today.getTime()) / 1000);
console.log(seconds);

let response = await fetch(fetchUrl.concat('?', paramString), {
method: "GET",
cf: {
cacheTtl: seconds,
cacheEverything: true,
cacheKey: url,
},
});
let headersObject = Object.fromEntries(response.headers);
let responseHeaders = JSON.stringify(headersObject, null, 2);
console.log(

Response headers: ${responseHeaders}

Response headers: ${responseHeaders}

);
return response;
}
} catch (err) {
return new Response('Error parsing JSON content', { status: 400 });
}"

V

Varna•4/24/24, 4:10 PM

I'm deploying via GitHub, got wrangler.toml:

# stuff above
compatibility_flags = ["nodejs_compat"]
[vars]
PROFILE_INFO = { baseURL = "https://example.com/", USER = "root", PASS = "toor" }
# more stuff below

# stuff above
compatibility_flags = ["nodejs_compat"]
[vars]
PROFILE_INFO = { baseURL = "https://example.com/", USER = "root", PASS = "toor" }
# more stuff below

# stuff above
compatibility_flags = ["nodejs_compat"]
[vars]
PROFILE_INFO = { baseURL = "https://example.com/", USER = "root", PASS = "toor" }
# more stuff below

# stuff above
compatibility_flags = ["nodejs_compat"]
[vars]
PROFILE_INFO = { baseURL = "https://example.com/", USER = "root", PASS = "toor" }
# more stuff below

but I fail to publish the project with error:

    Error: Failed to publish your Function. Got error: invalid or missing json property for binding PROFILE_INFO

    Error: Failed to publish your Function. Got error: invalid or missing json property for binding PROFILE_INFO

Also got warnings like

Your Worker may throw errors at runtime unless you enable the "nodejs_compat" compatibility flag.

Your Worker may throw errors at runtime unless you enable the "nodejs_compat" compatibility flag.

.

AAvinash Is there any way to intercept url query parameters (example.com/hello?name=joe) ...

I

IEatBeans•4/24/24, 4:40 PM

This is how I do it. Not intuitive but it works:

new URL(request.url).searchParams.get("days")

N

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

How do you get the rawBody of a request on a onRequest handler?

NNima How do you get the **rawBody** of a *request* on a onRequest handler?

H

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

In what format? A string? An ArrayBuffer?

HHello, I’m Allie!In what format? A string? An ArrayBuffer?

N

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

A string or a buffer is the response i get back that I need. It's for stripe constructEvent

NNima A string or a buffer is the response i get back that I need. It's for stripe con...

H

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

await ctx.request.arrayBuffer()

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

, not an

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()

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

Try putting your assets in a subdirectory

Similar Threads

Similar Threads

Similar Threads