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

However, that falls outside my scope. I can help with Pages not SSL for SaaS

It's not a problem with the certificate authority. When adding an IDN domain name, the message 'You must use a valid domain name.' is displayed. After conversion, the message 'You must use a hostname that is a part of your zone.' is displayed.

Spectrum cannot add an IDN domain name either, it prompts 'Invalid Domain'

Not sure about Spectrum

SSL for SaaS 100% can since you can on Pages and we use it

but again, this is not in my scope I'd recommend going to #1104040620948992090 and someone with more knowledge can help out

done

Noticed when I change a source file in

trpc/src/

folder, the log shows

✘ [ERROR] [proxy]: 

  [TypeScript] Found 0 errors. Watching for file changes.

When I modify

functions/trpc/[[endpoint]]/index.js

, I can see the whole page reloading.

I added the nodejs_compat flag in the functions settings both envs, but builds still fail