```ts export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next, data }): Promise<Re

export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next, data }): Promise<Response> => {
    let newRes = (await next()).clone();

    newRes.headers.set("Access-Control-Allow-Origin", "*");
    newRes.headers.set("Access-Control-Allow-Headers", "*");
    newRes.headers.set("Access-Control-Allow-Methods", "*");
    return newRes;
};

export const onRequest = [CORSHeaders];

export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next, data }): Promise<Response> => {
    let newRes = (await next()).clone();

    newRes.headers.set("Access-Control-Allow-Origin", "*");
    newRes.headers.set("Access-Control-Allow-Headers", "*");
    newRes.headers.set("Access-Control-Allow-Methods", "*");
    return newRes;
};

export const onRequest = [CORSHeaders];

export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next, data }): Promise<Response> => {
    let newRes = (await next()).clone();

    newRes.headers.set("Access-Control-Allow-Origin", "*");
    newRes.headers.set("Access-Control-Allow-Headers", "*");
    newRes.headers.set("Access-Control-Allow-Methods", "*");
    return newRes;
};

export const onRequest = [CORSHeaders];

export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next, data }): Promise<Response> => {
    let newRes = (await next()).clone();

    newRes.headers.set("Access-Control-Allow-Origin", "*");
    newRes.headers.set("Access-Control-Allow-Headers", "*");
    newRes.headers.set("Access-Control-Allow-Methods", "*");
    return newRes;
};

export const onRequest = [CORSHeaders];

CоleOP•4/18/22, 7:52 AM

I redeployed some other sites and all seems well, so I imagine I'm messing something up

CоleOP•4/18/22, 7:53 AM

all urls that aren't covered by a

function/

function/

work fine. every other URL automatically breaks. even the

404.html

404.html

is out

CоleOP•4/18/22, 7:56 AM

I added ls's and stat's to my

npm build

npm build

just to confirm that everything's there + permissions on the edge

CCоle ```ts export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next,...

Walshy•4/18/22, 9:24 AM

This is what I suspect is failing. If it is hitting everything it'll be the middleware.

Now it should work but there is an issue with next currently (https://github.com/cloudflare/wrangler2/pull/796 you can also try this build)
This should work:

export const onRequest = async ({ next }) => {
  let response = await next()
  const headers = new Headers([...response.headers.entries()])

  // set cors headers
  headers.set('x-new-header', 'new value')

  response = new Response([101, 204, 205, 304].includes(response.status) ? null : response.body, { ...response, headers })
  return response
}

export const onRequest = async ({ next }) => {
  let response = await next()
  const headers = new Headers([...response.headers.entries()])

  // set cors headers
  headers.set('x-new-header', 'new value')

  response = new Response([101, 204, 205, 304].includes(response.status) ? null : response.body, { ...response, headers })
  return response
}

RRui Saraiva Hi 👋 Is anyone getting an immediate error on the "Initializing build environme...

Walshy•4/18/22, 9:25 AM

Yo, what's the deployment ID? The UUID in the URL

RRui Saraiva Here it is: d54d0d44-8a67-4a4d-b1a5-0b322ec203a5

Walshy•4/18/22, 9:43 AM

We no longer have your GitHub installation anymore. Make sure Pages is still added as an App in your account and re-create the project

Ppaper clover it seems others are getting this on sveltekit with workers ``` Note: No function...

Walshy•4/18/22, 1:47 PM

Hey, can you provide me the deployment ID? (Check #

pages-faq for how to get it)

DDeleted User Hello!... I am having some issue with custom domain... If I add custom domain i...

Walshy•4/18/22, 1:47 PM

Do you have something like a redirect covering your custom domain?

Walshy•4/18/22, 1:52 PM

can you please send me the pages.dev and custom domain?

Walshy•4/18/22, 1:54 PM

Uncaught ReferenceError: process is not defined

Walshy•4/18/22, 1:54 PM

(and yeah... we need to improve the logs there)

Walshy•4/18/22, 1:55 PM

Yep

Walshy•4/18/22, 1:58 PM

wrangler pages dev

Walshy•4/18/22, 1:59 PM

You can also build locally with

wrangler pages functions build

wrangler pages functions build

Walshy•4/18/22, 2:02 PM

Looks like you have a bad CAA record on

aeonquake.eu.org

aeonquake.eu.org

Kian did a good message about this before

Walshy•4/18/22, 2:02 PM

pages-discussions

EExperimental Cyborg I'm stuck with this combo (gitlab on the left)

Walshy•4/18/22, 4:08 PM

what happens if you go through the "Connect GitLab" process again?

Original message was deleted

Walshy•4/18/22, 4:08 PM

what page was that?

export const onRequest = async ({ next }) => { let response = await next() const headers = new Headers([...response.headers.entries()]) // set cors headers headers.set('x-new-header', 'new value') response = new Response([101, 204, 205, 304].includes(response.status) ? null : response.body, { ...response, headers }) return response }

```ts export const CORSHeaders: PagesFunction<{}> = async ({ request, env, next, data }): Promise<Re

Similar Threads

Similar Threads

Similar Threads