Hey folks, it's been a while since the topic of Zola last came up - fully supported in v1, supported in v2 via a workaround (seems zola build is not working), any chance of seeing it fully supported any time soon?
Please do not post your question in multiple channels per the rules at No Access. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
Guys! Brotli compression is not available in Pages. Even if I have compressed files, CF always serve the gzipped version of the files. Is this a feature only for Enterprise Plans?
Hey there, im a bit confused about the subrequest using fetch in cloudflare pages / nuxt3 application. If I have understood this correctly subrequests using fetch triggerd within a worker/cf pages should respect the cache by default?
When i curl my url (e.g.
https://my-domain.com/api/proxy/foo
https://my-domain.com/api/proxy/foo
i get a response where the header
cf-cache-status
cf-cache-status
is present. Doin the same request with fetch within my pages application, pointing to itself (using the external url), does not return a
cf-cache-status
cf-cache-status
header, it's just not present.
I can see in the logs that the main request is hitting my pages application and the subrequest also. What I would expect is to only see the main request and the subrequest is cached, so never reaches the application.
Calling the url from outside again (using my curl), does not create any new logs, so it is cached as expected.
Just Pages, but granted, the ones that are just proxied via CF (so no Pages) are pinged from Falkenstein (Hetzner). A non-CF website doesn't show increased TLS handshakes in AMS3
either or .. im tryingto see if there's any examples someone made of doing it , for workers for platforms if i wanted to deploy a static frontend if there was a way to do it programatically via REST API for pages
Is there some easy way to prevent downtime for users already on a CF page when a new deployment is pushed? Users tend to get 404s if thet happen to be already on-page when the deployment is updated
Can anyone help me troubleshoot why I'm getting 'inactive (error)' when i try to link a namecheap domain to a cloudflare page? I have the domain linked to the correct cloudflare nameservers and i'm confident my CNAME record is setup correctly. @Walshy I've read multiple forum threads you were engaged in over the past few years on this issue but I havent been able to resolve this