Please do not ping anyone for help, this is a volunteer community and people will help as and when t

EErisa Please do not ping anyone for help, this is a volunteer community and people wil...

ز

زين•12/22/23, 11:54 AM

ok thank you

ز

زين•12/22/23, 7:42 PM

...

Ssavtrip Hey guys, I am migrating websites to cloudflare that utilise the same API keys, ...

A

Ashley•12/24/23, 11:44 PM

Not sure where it’s at / if it’s in beta yet, but https://blog.cloudflare.com/secrets-store is what you want when it’s available I think

The Cloudflare Blog

Announcing Cloudflare Secrets Store

Introducing Secrets Store by Cloudflare - the ultimate solution for managing your application secrets securely. Safeguard sensitive information, track access, and maintain ease of use.

AAshley Not sure where it’s at / if it’s in beta yet, but https://blog.cloudflare.com/se...

S

savtrip•12/25/23, 11:40 PM

@ScaredOfMyRawr thanks for that, exactly what I’m looking for, appreciate you linking it

Bbondero I got a `_middleware.js` auth function catching requests that don't have an auth...

I

Isaac McFadyen•12/27/23, 9:54 PM

So the reason this occurs is because _middleware.js runs on the server, and the server has no way to know the domain in this case.

I

Isaac McFadyen•12/27/23, 9:55 PM

You'll need to provide an absolute path somehow. If you don't want to hardcode the value in I'd recommend using environment variables (https://developers.cloudflare.com/pages/functions/bindings/#environment-variables).

Bbondero envvars is another way of hardcoding, i'd like to possibly derive from existing ...

J

James•12/27/23, 10:19 PM

You can pass a base URL to

new URL

new URL

as the second parameter, so you could do something like:

const redirectURL = new URL('/login/', 'https://example.com');
return Response.redirect(redirectURL.toString());

const redirectURL = new URL('/login/', 'https://example.com');
return Response.redirect(redirectURL.toString());

const redirectURL = new URL('/login/', 'https://example.com');
return Response.redirect(redirectURL.toString());

const redirectURL = new URL('/login/', 'https://example.com');
return Response.redirect(redirectURL.toString());

J

James•12/27/23, 10:20 PM

You might want to do a

new URL(context.request.url)

new URL(context.request.url)

, and then pass the

.hostname

.hostname

of that into that new constructor, or just override its

.pathname

.pathname

etc. to construct your redirect URL

J

James•12/27/23, 10:21 PM

Relative URLs are technically permitted nowadays too in the

location

location

header, so perhaps even this could work (untested):

return new Response(null, {
    status: 302,
    headers: {
        location: '/login/',
    }
});

return new Response(null, {
    status: 302,
    headers: {
        location: '/login/',
    }
});

return new Response(null, {
    status: 302,
    headers: {
        location: '/login/',
    }
});

return new Response(null, {
    status: 302,
    headers: {
        location: '/login/',
    }
});

J

James•12/27/23, 10:29 PM

you're hard-coding the length to

, which will likely break depending on your domain

J

James•12/27/23, 10:29 PM

I would recommend one of the solutions I pasted above which should be way more stable

A

Akash•12/28/23, 3:50 AM

If we terminate a request in a functions middleware before it hits any function, is it going to be counted as a billable invocation?

J

James•12/28/23, 4:19 AM

If a worker is spun up to run your code, you’ll be billed (under the hood Functions uses Workers). I guess if you terminate the request early enough before it’s made a connection and the worker is spun up, you’d avoid an invocation

U

Unsmart•12/28/23, 5:23 AM

Middleware is run in the worker though isn’t it

U

Unsmart•12/28/23, 5:24 AM

So it would count as an invocation

A

Akash•12/28/23, 6:02 AM

that is my understanding as well but wanted a confirmation. I am trying to figure out a way to avoid invocation by bots and other malicious actors so that it does not consume worker quota. WAF seems to be the first line of defense in such cases but not sure if it can keep all such actors away from consuming your paid (compute) infrastructure.

I

Isaac McFadyen•12/28/23, 1:02 PM

Yes, middleware is run in the Worker as well so you'll be billed.

AAkash that is my understanding as well but wanted a confirmation. I am trying to figur...

S

subscriptions•12/28/23, 1:29 PM

I'm also looking for this, is there a way to cache the worker output somewhere which does not cost for invocation on further calls?

Kkingmesal I have an `await` on my call to the worker binding

S

schkovich•12/29/23, 2:24 AM

did you resolve it?

i have the same problem

K

kian•12/29/23, 2:24 AM

If you mean that your Service Binding subrequests are showing

canceled

canceled

, make sure you read the response body (even if you don't need it).

Kkian If you mean that your Service Binding subrequests are showing `canceled`, make s...

S

schkovich•12/29/23, 2:35 AM

thank you! it makes sense, but it would not cross my mind anytime soon.

Sschkovich did you resolve it? 🤔 i have the same problem 😄

K

kingmesal•12/29/23, 1:52 PM

Still get the cancelled message... But we'll try that new suggestion...

Kkingmesal Still get the cancelled message... But we'll try that new suggestion...

S

schkovich•12/29/23, 2:22 PM

I couldn't find such a restriction in fetch API. Most likely, this behaviour is cloudflare

undocumented implementation detail. Like providing dummy properly formatted URI in fetch request to desired Service Binding. Nevertheless, @kian suggestion worked.

T

Tudders•12/30/23, 1:52 AM

Hey all - wondering if anyone has gotten the openAI includes to work in functions ala -> https://developers.cloudflare.com/workers/tutorials/openai-function-calls-workers/ ?

My build is erroring out looking for the packages -> utils/chatGPT.js:6:24: ERROR: No matching export in "../node_modules/openai/index.mjs" for import "OpenAIApi" ...

SOLVED blobyes

OpenAI GPT function calling with JavaScript and Cloudflare Workers ...

All of the tutorials assume you have already completed the Get started guide, which gets you set up with a Cloudflare Workers account, C3 , and …

E

Esteban 🇨🇺•1/2/24, 6:11 PM

Anyone want to chime in why this Pages Function works with GET but with POST it returns CORS errors.

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

function generateUUID() {
  return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(/[xy]/g, function (c) {
    var r = (Math.random() * 16) | 0,
      v = c == 'x' ? r : (r & 0x3) | 0x8;
    return v.toString(16);
  });
}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });
  
  response.headers.set('Access-Control-Allow-Origin', '*');
  
  return response;

}

E

Esteban 🇨🇺•1/2/24, 6:30 PM

~~I'm somewhat certain this is not a traditional Browser CORS issue. Instead it's an issue of Cloudflare arbitrarily re-imagining how CORS is configured on their platform.~~

I eagerly await support, as no Googling or ChatGPT is helpful here.

J

James•1/2/24, 6:32 PM

Can you provide the error you receive in your browser when attempting to hit it? A screenshot of your browser console might be helpful

E

Esteban 🇨🇺•1/2/24, 6:33 PM

Network Tab.

Screen_Shot_2024-01-02_at_1.32.38_PM.png

E

Esteban 🇨🇺•1/2/24, 6:33 PM

Console. At this point, I don't care about showing my domain.

Screen_Shot_2024-01-02_at_1.33.08_PM.png

K

kian•1/2/24, 6:34 PM

This is nothing to do with Cloudflare, you just haven't setup preflight handling.

K

kian•1/2/24, 6:35 PM

https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request

K

kian•1/2/24, 6:35 PM

Primarily https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers

J

James•1/2/24, 6:35 PM

I'd recommend you lock it down more tightly than this, but a baseline to get things working during testing should be:

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

    'Access-Control-Allow-Origin': '*',
    'Access-Control-Allow-Headers': '*',
    'Access-Control-Allow-Methods': 'GET,HEAD,POST,OPTIONS',

E

Esteban 🇨🇺•1/2/24, 6:36 PM

I'll give it a shot

E

Esteban 🇨🇺•1/2/24, 6:36 PM

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

export async function onRequest(ctx) {

  const response = Response.json({ response: { session: generateUUID() } });

  response.headers.set("Access-Control-Allow-Origin", "*")
  response.headers.set("Access-Control-Allow-Headers", "*")
  response.headers.set("Access-Control-Allow-Methods", "GET,HEAD,POST,OPTIONS")

  return response;

}

Updated onRequest

E

Esteban 🇨🇺•1/2/24, 6:38 PM

It worked. I take back what i said.

J

James•1/2/24, 6:40 PM

Glad you got it working

W

Will•1/3/24, 10:57 AM

So I have an SSR site made with astro.
let's on the server side rendering I need to access worker KV.

now I have two options :

use pages function(I am still not sure how is this going to work tbh, but it looks like astro made a js file under function folder)
make a worker then bind that to the astro pages.

what is the pros and cons of both option?

Q

quambo•1/3/24, 12:21 PM

Quick question around

pages dev

pages dev

pages dev

pages dev functions and restarting on code changes.

I've got a function that re-exports

onRequest

onRequest

from a different folder, and I use the wrangler dev bundling. The details are here: wrangler pages dev when functions are not in root?

For some reason during dev, codechanges are not applied without having to restart. Is this a bug?

N

NoOneInParticulate•1/9/24, 8:27 PM

I have a page with a simple function using

export async function onRequestPost(context) {

export async function onRequestPost(context) {

export async function onRequestPost(context) {

export async function onRequestPost(context) { I am trying to POST some JSON to it. While logging

context

context

or

context.request

context.request

context.request

context.request, or

context.request.body

context.request.body

context.request.body

context.request.body I don't see the data I am passing in from a POST via curl or Postman.

I'm not seeing enough information in the docs to help me understand what I'm doing incorrectly.

Thanks!

NNoOneInParticulate I have a page with a simple function using `export async function onRequestPost(...

K

kian•1/9/24, 8:31 PM

context.request

context.request

context.request

context.request is the Request Web API, where the

body

body

property is a ReadableStream

K

kian•1/9/24, 8:32 PM

If you want to access the body, there are helper methods on

Request

Request

Request

Request like

text()

text()

text()

text() &

json()

json()

json()

json(). So, if your request body is JSON, then you'd do...

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

const json = await context.request.json()
console.log(json.property);

Please do not ping anyone for help, this is a volunteer community and people will help as and when t

Similar Threads

Similar Threads

Similar Threads