try replacing it with

return Response.redirect(matchedUrl.url, 302);

ok ... just updated wrangler to v3 and I can't get Pages to work anymore. What's the breaking change? I have an index.ts in my functions folder exporting an onRequestGet: PagesFunction and when I run with

wrangler pages dev ./static

I get a 404

oh ignore me ... being an idiot!! I wrote

onRequetGet

instead of

onRequestGet

wish there was some typing for the exported supported PagesFunction names seeings as they are explicit.

Hello, having an issue as well with running a pages site and functions locally using: wrangler pages dev dist/cloudflare --compatibility-date=2021-09-20 when I try to hit my functions URLs I am getting my not found page on the site. if I change dist/cloudflare to just dist, I can get the function to run but no pages site. Any help is appreciated!

spent a little time experimenting and got it running using this COMMAND feature. Seems like a wild way to have to run this but got it working with: wrangler pages dev --proxy 8789 --compatibility-date=2021-09-20 --d1=DB --persist-to=db.sqlite -- wrangler pages dev dist/cloudflare --compatibility-date=2021-09-20 --port 8789

Are you using a framework, by chance?

It sounds like your Functions folder is in the wrong place

Does Cloudflare support Mongoose?

No, because Mongoose uses TCP connections. They actually are supported now in Workers/Functions, but because it's a non-standard API the package has to support it as well, and as far as I know Mongoose/MongoDB doesn't do that yet.

Does Cache API with custom cache-control work on pages.dev (preview)? Because it cached as it should, but isn't expired after 60 seconds

ts
export const getContacts = async (
    CF: WorkerRuntime<Env> | PagesRuntime<Env, unknown>
): Promise<string | null> => {
    const cache = await caches.open("pages");

    const cacheKey = `https://example.com/pages/contact`;

    const cachedAbout = await cache.match(cacheKey);
    if (cachedAbout) {
        console.log("CACHE");
        return await cachedAbout.json();
    }

    console.log("non-cache");

    const contact = await CF.env.SETTINGS.get<string>("pages/contact");

    CF.waitUntil(
        cache.put(
            cacheKey,
            new Response(JSON.stringify(contact), {
                headers: { "Cache-Control": "max-age=60" },
            })
        )
    );

    return contact;
};

It can only go as low as your zone plan allows

considering > on pages.dev (preview) I would think it would be held to the limitations of the free plan in that case

So it would be min. 2 hour (edge cache) for free, thanks.

did you figure out how to make this work?

Let me see if I can find that project! It's been a while, and I can't remember if I ended up fixing it.

How about Prisma with Cloudflare pages? can't I use it instead of Mongoose and connect it to MongoDB or It wont work either

Same thing. Even though it's a different library it still needs to connect to MongoDB over TCP, and as far as I know Prisma hasn't implemented that yet.

If they have a place for feature requests you could submit that.

I have encountered an issue while using the Cloudflare Pages feature. When I tried to add an Internationalized Domain Name (IDN), I was unable to successfully add it to my page. I also attempted to convert the IDN to Punycode, but the problem still persists.

what's your pages.dev?

idndemo.pages.dev

An unknown error occured. Contact your account team or Cloudflare support: https://cfl.re/3WgEyrH. (Code: 8000000)

xn--0zwm56d.xyz

try again now

Other accounts are unable to add.

you still can't add it?

Yes, on another account

In SSL/TLS Custom Hostnames and Fallback Origin, it is not possible to use IDN domain names

It is

But you may be selecting a CA which doesn't support it