Cloudflare Developers•3y ago

but this is not possible ..

ConstantinOP•12/16/23, 4:08 PM

thats why i created a tenant.app.nefele.ai worker .. then create a wildcard on top of it ..

ConstantinOP•12/16/23, 4:12 PM

oh, it does work when adding via pages interface

ConstantinOP•12/16/23, 4:23 PM

huh

ConstantinOP•12/16/23, 4:24 PM

what about this pair .. this should have worked, right?

CConstantin but this is not possible ..

Erisa•12/16/23, 4:39 PM

Remove the "custom_domain": true"custom_domain": true and set the pattern to *.app.nefele.ai/**.app.nefele.ai/*

Erisa•12/16/23, 4:40 PM

I mentioned this here -> pages-discussions

ConstantinOP•12/16/23, 4:47 PM

you're smart! thank you

ConstantinOP•12/16/23, 4:49 PM

now, if i'm thinking .. having the worker in between domain and page is a smart way to allow future opaque changes

Erisa•12/16/23, 5:33 PM

Indeed

kian•12/16/23, 8:00 PM

The Cache API (caches.defaultcaches.default, etc) don't set a CF-Cache-StatusCF-Cache-Status header.

kian•12/16/23, 8:00 PM

If you're seeing that, it's from the subrequest you made in the Worker.

Unsmart•12/16/23, 8:20 PM

set your own header with like x-workers-cache or something

Unsmart•12/16/23, 8:24 PM

its not really a bug from the perspective of the proxy it is a cf-cache-status of dynamic because the proxy isnt caching the response and wont

kian•12/16/23, 8:29 PM

What's the URL of the Worker that receives CF-Cache-Status: HITCF-Cache-Status: HIT?

Unsmart•12/16/23, 8:30 PM

Workers can override CF- headers yeah I think if anything thats the bug.

Unsmart•12/16/23, 8:30 PM

The difference is workers run before the proxy and pages functions run after the proxy

Unsmart•12/16/23, 8:35 PM

Pages is considered an origin because you set a DNS record and it has to hit the DNS to get the response.

Workers can completely ignore your DNS record and never call it if you wanted.

Unsmart•12/16/23, 8:58 PM

The zone its on doesnt matter at all. Workers are not an origin. Pages is an origin. Workers do not go through the proxy. Pages goes through the proxy. When you go through the proxy the CF-Cache-Status header will be what the proxy cache status is. When you dont go through the proxy it will be whatever you set.

Unsmart•12/16/23, 9:08 PM

Its a fake "origin" it doesnt go through the proxy. It just means you dont have to set your own fake origin for custom domains.

Unsmart•12/16/23, 9:41 PM

pages.dev doesnt go through the proxy thats why. The custom domains do.

Unsmart•12/16/23, 9:41 PM

pages.dev can be considered the worker technically

Unsmart•12/16/23, 9:42 PM

If you use CF for saas on top of your worker it would behave the same as pages + custom domain because thats what pages is.

Unsmart•12/16/23, 9:52 PM

not really the proxy doesnt take that long

but this is not possible ..

Similar Threads

Similar Threads

Similar Threads