my pages are exceeding 100k requests which are on our current plan. Do we need to upgrade?
my pages are exceeding 100k requests which are on our current plan. Do we need to upgrade?
DIt seems like everything we host on pages is static
HAre you using a framework?
Datm our pages are deployed with sveltekit and I believe one page is no framework
HThat might be the issue. IIRC SvelteKit doesn't support fully-static builds. If your projects are entirely static, I would probably look into using something like https://astro.build
Astro
Astro builds fast content sites, powerful web applications, dynamic server APIs, and everything in-between.
DTheres no issue atm, just wondering if there will be. Our pages seem to work fine
D0% Errors, 100% success, 200k requests for the last 24 hours
D150k/100k
Fcan someone please explain me a bit about how URLs work in CF pages?
Fi'm trying to redirect
x.com/*/ to x.com/* (remove trailing slash), but it's causing a "too many redirects" issueFit's looping, why?
Fwhy is that?
Fso CF redirects
/index.html/and it is not possible to remove the trailing slash somehow?
Fbut that causes SEO issues, as is not the same as the canonical url
Foh that's what i mean, i'm getting a "too many redirect" when using the transform rule
Fi don't want to change the canonical urls now, that's so bad
Fplus i don't like the ending slash anyway
Fwhy the transform rule doesn't work?
Fit's weird that CF forces me to use the canonical url they want..
Fat least there is a solution
Fi found this:
Pages will also redirect HTML pages to their extension-less counterparts: for instance, /contact.html will be redirected to /contact, and /about/index.html will be redirected to /about/.
Fi just have to move all my files xD
_Do tail workers or logpush work with pages?
_nvm found with a better search. looks like no as of last month
EIts still not currently supported
_thanks. is there a roadmap or plans for that support?
ISvelteKit does support fully static builds by way of
@sveltejs/adapter-static.IIf you want to switch over then as long as all of your pages are static it should work.
Ccan someone help me on SvelteKit 
fetchglobal
fetch/api/api
Ghttps://developers.cloudflare.com/pages/how-to/web-analytics/
Is web analytics for static sites free? Or is there a limit based on traffic?
Is web analytics for static sites free? Or is there a limit based on traffic?
Cloudflare Docs
Cloudflare Web Analytics provides free, privacy-first analytics for your website without changing your DNS or using Cloudflare’s proxy. Cloudflare Web …
JHey guys, how can I troubleshoot why my pages deployment gives a "Connection timed out Error" 522?
The pages direct upload CLI says successful and provides a url, but the dashboard says deploy failed.
It has a cdn-cgi/errors/no-nodejs_compat.html file but the flag is set in the dashboard
Example failing deploy ID:
What's strange is that I have (what I think) is that same exact commit deployed to another account, ID:
it works fine locally with
Looks like https://github.com/cloudflare/workers-sdk/issues/4583 ?
The pages direct upload CLI says successful and provides a url, but the dashboard says deploy failed.
It has a cdn-cgi/errors/no-nodejs_compat.html file but the flag is set in the dashboard
Example failing deploy ID:
68e29d28-44af-4419-b1b5-b319f3a97338What's strange is that I have (what I think) is that same exact commit deployed to another account, ID:
83e8c4bb-0aa1-4887-9c88-d840cd7d4e16 That has the same error file but built and serves up a 200 just fineit works fine locally with
bunx wrangler pages dev .vercel/output/static --compatibility-flags="nodejs_compat"Looks like https://github.com/cloudflare/workers-sdk/issues/4583 ?
GitHub
The functions/workers in Cloudflare Pages have the same 1MB limit as the normal workers on free accounts. But while you get a warning/errors for normal workers, you don't for Cloudflare Pages r...
ZIs the plan for the pages-part of the CLI to align with Workers at some point? It's been a while since I used Pages, and I just remembered that I needed to use the dashboard, and not the CLI/wrangler-config, to configure my compatibility flags.
The "next-on-pages" guide on developers.cloudflare.com (https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/) kinda hints that you can set compat flags via inline arguments to wrangler CLI or set via wrangler.toml, but the readme for the package actually says that I need to go via the dashboard (https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflarenext-on-pages). I know that the truth is via the dashboard, but it would be neat if either the CLI is updated, or the official docs are updated
The "next-on-pages" guide on developers.cloudflare.com (https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/) kinda hints that you can set compat flags via inline arguments to wrangler CLI or set via wrangler.toml, but the readme for the package actually says that I need to go via the dashboard (https://github.com/cloudflare/next-on-pages/tree/main/packages/next-on-pages#cloudflarenext-on-pages). I know that the truth is via the dashboard, but it would be neat if either the CLI is updated, or the official docs are updated
JI'm using Remix w/Workers Sites (that was the best/only choice 2+ years ago). Now the recommendation from 
is to use Pages for all new full stack development. Remix has built on that to say that Remix w/Vite (essentially all future Remixes) only officially support Pages https://github.com/remix-run/remix/pull/8531#issuecomment-1894517373. I'm trying to identify the gaps between Workers and Pages. Is there any where I can see a comparison between the two, or can anyone help me with the differences in features?
For example, we use Tail Workers to send logs to Datadog but those aren't supported in Pages. Are there other products which Workers can use but Pages cannot?
is to use Pages for all new full stack development. Remix has built on that to say that Remix w/Vite (essentially all future Remixes) only officially support Pages https://github.com/remix-run/remix/pull/8531#issuecomment-1894517373. I'm trying to identify the gaps between Workers and Pages. Is there any where I can see a comparison between the two, or can anyone help me with the differences in features? For example, we use Tail Workers to send logs to Datadog but those aren't supported in Pages. Are there other
products which Workers can use but Pages cannot?GitHub
This currently relies on wrangler@beta, so let's wait to merge this until the next stable release of wrangler that includes getBindingsProxy. CF core team says that should happen next week or s...
KWorkers typically have new bindings first, i.e Pages doesn't have Hyperdrive
KPages Functions can't have scheduled handlers, email handlers, Queue consumer handlers, etc
KThey're mostly the same thing other than that though
JAny ETA for Tail Workers in Pages? Or suggestions/references for how people send the logs to Datadog/Sentry/etc in Pages? I guess a application logging/debugging function could send those to a queue and have something else process them? But I really like just using console.{debug,log,info,error} all over and having those automatically collected and sent somewhere else for processing. Especially b/c it automatically parses JSON, etc
AHi all - I was wondering if it may be worth discussing issues with Cloudflare Pages running
This occurs almost consistently most recently and it begs the question - why is a build command running that the developer has not specified? It's impossible to debug (such as appending the
bun install --frozen-lockfileFailed: build exceeded the time limit and was terminated. Refer to https://developers.cloudflare.com/pages/platform/limits/#builds for build limits
This occurs almost consistently most recently and it begs the question - why is a build command running that the developer has not specified? It's impossible to debug (such as appending the
--verbose flag) because we have no choice in the matter. This seems like a questionable technical decision?Cloudflare Docs
Below are limits observed by the Cloudflare Free plan. For more details on removing these limits, refer to the Cloudflare plans page.
SI'm trying to find API docs for
But I can't find anything, nor cloudflare-go seems to have any bindings.
Is this a private API of shorts?
/pages/assets/* (https://github.com/cloudflare/workers-sdk/blob/040be5d20cf5c34976dd525c93703910c416545a/packages/wrangler/src/pages/upload.tsx#L216)But I can't find anything, nor cloudflare-go seems to have any bindings.
Is this a private API of shorts?
GitHub
Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk
Home to Wrangler, the CLI for Cloudflare Workers® - cloudflare/workers-sdk
CIt’s one of the undocumented ones. You can reverse engineer it to use but there is no compatibility guaranteed.
SI see, Maybe I'll shell out to wrangler to do the job for now, and only hit the API to get the information I need, (URLs and such).
MCan I password-protect my page sites with a combination of user-id-passwords like with htaccess and htpasswd? Is there any way in Cloudflare to do that?
Dyou can use cloudflare access to limit who can see your page, including preview deployments: https://developers.cloudflare.com/pages/functions/plugins/cloudflare-access/
VI'm deploying a Remix app to Pages that uses a TOTP package which relies on the package
thirty-two for base32 encode/decoding. The thirty-two package uses the Node.js Buffer library but doesn't import it like 'node:buffer' (it doesn't import it at all) because it is a global library. I'm getting ReferenceError: Buffer is not defined despite using the nodejs_compat compatability flag. How do I figure this out?
THi, i have a asset (mp4 video) with a size of 42 mb, thats not supported by CloudFlare pages, where should i host that video on for the best speed results?
CYou could throw it on Cloudflare R2, with an R2 Custom Domain making it public on your own domain
CYou could use Stream as well if you wanted its player/transcoding/etc, but that's more expensive, espec for one video/you may not want all that stuff
TOkay thanks!
