Is there any way to make it block access to: myproject.pages.dev?
(i.e. the production deployment that doesn’t have a custom domain)
I’m considering a workaround of committing a blank index.html to a branch and setting that for the production deployment. But I’d prefer to have access to myproject.pages.dev to run speed tests, etc on a consistent domain.
Update: that works for pre-launch, but this is still a problem in production because this content is available at another URL.
Have you tried creating an access rule that blocks access to the pages.dev with an authentication policy?
Yes. Just make an access policy with the pages.dev 