IIRC the confirmation phase is just issuing the cert
IIRC the confirmation phase is just issuing the cert
HSo you can’t really skip it
BAny ideas on why
devdeploy doesn't like import attributes?
Dprobably because wrangler is still using an ancient esbuild version :/
BThanks for pointing me in that direction - that is indeed the issue. Looks like getting on
0.19.x
DIs there any issue where this is being tracked yet?
DThere is an issue (https://github.com/cloudflare/workers-sdk/issues/5222), and there used to be an experimental PR but they closed that (https://github.com/cloudflare/workers-sdk/pull/5361)
AI'm reading Pages' docs and I can't find a way to make the server return a proper 404 http code in an asset that doesn't exist is requested.
According to https://developers.cloudflare.com/pages/configuration/serving-pages/#not-found-behavior I can create a custom 404.html that can display a "404 not found" message to the user, but the actual http code is still 200.
And according to https://developers.cloudflare.com/pages/configuration/serving-pages/#single-page-application-spa-rendering if I don't provide any 404.html, cloudflare will return the index.html for all requests that don't match any file.
So... how can I make Pages return a real 404 http code?
According to https://developers.cloudflare.com/pages/configuration/serving-pages/#not-found-behavior I can create a custom 404.html that can display a "404 not found" message to the user, but the actual http code is still 200.
And according to https://developers.cloudflare.com/pages/configuration/serving-pages/#single-page-application-spa-rendering if I don't provide any 404.html, cloudflare will return the index.html for all requests that don't match any file.
So... how can I make Pages return a real 404 http code?
Ethe status code of
/404/asdfgoh, I thought
/asdflet me check
EIt shouldnt
Ehttps://erisa.uk/asdf for example
Aoh it does!! (I just tried with my page)
Athank you 
EWhat error do you get?
CPages doesn't flush cache at all on your custom domains for you
CIt's recommended you disable it with a cache rule if you're having issues with it
Cpossible that the html propagated more quickly then the resources, leading to a request for the asset when it didn't exist yet, Pages served the default html (spa behavior) and your zone cached it. For Pages, your Custom domain's/zone's caching behavior is all on top of it/out of its concern. The Cf-Cache-Status is entirely from your Custom domain
Cyea, I've only seen a few reports of this recently as well, could be KV propagating slower. Regardless, all of what I said remains the same
CDefault Cache settings only cache specific extensions https://developers.cloudflare.com/cache/concepts/default-cache-behavior/ like js/css/etc, not HTML, which is why that part wouldn't be effected/cached
Cno, and it really shouldn't be anything you have to worry about either. If you make a Cache Rule for your hostname marking as ineligible, you won't have issues with your zone/custom domain cache getting in the way, and Pages uses KV under the hood which has its own cache (not reflected in the headers) to keep things speedy
(and Page's own KV cache is by unique asset/not just by path/smart enough to not hit the same issues)
(and Page's own KV cache is by unique asset/not just by path/smart enough to not hit the same issues)
CYour main page is html, which already isn't cached by default. The issues is the assets, cs/jss/etc specifically.
You'd want a Cache rule disabling cache on the entire hostname
You'd want a Cache rule disabling cache on the entire hostname
CSorry I know this might be a bit confusing/weird, it's been a quirk of Pages forever, and more annoying if you have static resource names like /home.css and such as you'd hit it on every redeploy. There's just no tie in between your Custom Domain/Zone cache and Pages Cache, ex:
User -> Cloudflare -> Cloudflare Website Cache -> Cloudflare Pages -> Internal Worker using KV/KV Cache
User -> Cloudflare -> Cloudflare Website Cache -> Cloudflare Pages -> Internal Worker using KV/KV Cache
CPages has KV Cache, which is also using local cache
CCloudflare treats Pages as a normal origin/webserver, and then Pages itself uses KV for storing/retrieving assets which has its own cache, which is why you end up with 2 layers of cache on Custom Domains
CIn a perfect world Pages would just disable cache entirely on your Custom domain through some magical integration, sadly we're not there yet. This specific issue with assets not existing and getting wrongly cached 404s/200 SPA responses has been something newer though. We escalated it once before and don't think we got a specific response on it/eventually the asset just replicated and worked, seems that its just slower sometimes now to replicate which allows your custom domain cache to cache the wrong thing
Zi need to move a custom domain from one pages project to another... can I do this by just adding it to the new project? Or will I need to remove it from the first one first? And will this incur any downtime?
HIf they are on the same account then it should be a smooth transition
CIt's the same CF for SaaS so it has two stages:
- Verifying the cname is pointed at it "ownership validation"> https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/domain-support/hostname-validation/
- and then issuing the cert > https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/security/certificate-management/issue-and-validate/validate-certificates/
CYou don't need to actually wait for the second part if you have a universal covering it, it can even fail entirely and it'll say Errored in your Custom Domains page but work fine, so all you really care about is the first phase
Cand the first phase is just a combination of
How fast is the DNS Update in coordination with how fast is the Custom Hostnames Queue and their retry schedule (longer it takes, more it'll back off)
How fast is the DNS Update in coordination with how fast is the Custom Hostnames Queue and their retry schedule (longer it takes, more it'll back off)
CI track how long it takes to setup a new Custom Hostname here: https://customhostnames.cloudflare.chaika.me/ fwiw, that's purely the first step, no ssl. That's not accounting for DNS Propagation though, that test works off the CNAME already existing
C(and just in case it's worth mentioning, Pages forces CNAME real-time verification and HTTP Validation)
VY'all, how do you approach profiling / performance optimizations of your apps? I have a Remix app and I'm wondering how to tackle some slow pages in a reasonable way that shows full stack traces somehow.
Atest
Aya'll don't like links do you 
Aloginsessionsource[dot]pages[dot]dev/?source_IDjhjghYTRERTYU_search=cloudflare@ismoronic[dot]com --- how do you report phishing? Is there any policing on this platform or is it the same as the IPFS gateway - any loser 14 year old russian script kiddie can phish for passwords?
FIf you feel that a site is engaging in illegal or inappropriate activities, you can submit an abuse report at https://abuse.cloudflare.com/. The Trust and Safety team will review the details and reply if appropriate. You can also report the site to your relevant local authorities. Reports cannot be filed via Discord or with individual employees or Champs.
Cloudflare
Where to file DMCA, trademark, phishing and malware complaints with Cloudflare
ADisgusting.
