Got an update to this. My original build had ~2500 files and everything was uploaded successfully th

Got an update to this. My original build had ~2500 files and everything was uploaded successfully through wrangler. Several random js and css files got 500-error however when accessing them. The amount of files are due to articles on the site.
I did a test now and only prerendered part of the articles, ending up with 1050 files, and deployed that. Now everything on CF works and there are no 500-errors, but I need to be able to publish all my articles.

DDiAvisoo Got an update to this. My original build had ~2500 files and everything was uplo...

harshjv•6/9/24, 12:20 PM

Number of files shouldn't be an issue. CF Pages allows up to 20,000 files (https://developers.cloudflare.com/pages/platform/limits/#files)

harshjv•6/9/24, 12:21 PM

I had to roll back to a previous deployment since all new deployments have this issue, but i need to deploy ASAP

DDiAvisoo Got an update to this. My original build had ~2500 files and everything was uplo...

Walshy•6/9/24, 1:04 PM

very confused why this is happening... can you please share a repro URL?
Same for you @harshjv

Walshy•6/9/24, 1:05 PM

(actually moving to forum, easier to track - https://canary.discord.com/channels/595317990191398933/1249285733416439838)

TothW•6/9/24, 1:18 PM

Hello everybody I am a little bit confused. I have this WAF rule to bloc all requests from HTTP/1.0 and HTTP/1.1 but I see some events first went through bot fight mode, cloudflare gave the managed challenge and then passed my WAF even though the request came from HTTP/1.1. Is there any way to block this?

Walshy•6/9/24, 1:21 PM

That's only blocking HTTP rather than HTTPS

Walshy•6/9/24, 1:22 PM

You can use HTTPS over HTTP/1.1

Walshy•6/9/24, 1:22 PM

(HTTP just means HTTP requests over plain text while HTTPS is HTTP encrypted)

Walshy•6/9/24, 1:22 PM

There's probably a protocol version field or something you can use

Walshy•6/9/24, 1:23 PM

ah yeah:

Walshy•6/9/24, 1:23 PM

https://i.walshy.dev/hdf4oTNUBMCFhgQsUN.png

Walshy•6/9/24, 1:23 PM

"HTTP Version"

Walshy•6/9/24, 1:23 PM

do a rule like that and you can block /1.0 and /1.1

Walshy•6/9/24, 1:24 PM

(also, this is not the right channel for WAF stuff - this is for the Pages product -- general-discussions )

TothW•6/9/24, 1:36 PM

You are right, thank you. Yes, my bad, I've asked here because I am trying to set up the security for a cloudflare page MeowHeartCloudflare

. I will use the other channel.

cosetto•6/9/24, 2:37 PM

Hello everyone, I have a question to ask.
How to make r2 become a resource folder in page?
For example, my page is "example.page.dev", and I want to access the r2 files under "example.page.dev/asset"

RraRaRa I kinda wish it was just like S3 or any other origin, where it doesn't need to "...

Hello, I’m Allie!•6/10/24, 8:51 AM

IIRC the confirmation phase is just issuing the cert

Hello, I’m Allie!•6/10/24, 8:51 AM

So you can’t really skip it

bkspace•6/10/24, 10:34 AM

Any ideas on why

dev

dev

deploy

deploy

doesn't like import attributes?

Bbkspace Any ideas on why `dev` or `deploy` doesn't like import attributes?

DaniFoldi•6/10/24, 11:09 AM

probably because wrangler is still using an ancient esbuild version :/

DDaniFoldi probably because wrangler is still using an ancient esbuild version :/

bkspace•6/10/24, 11:47 AM

Thanks for pointing me in that direction - that is indeed the issue. Looks like getting on

0.19.x

0.19.x

+ still needs some work.

Bbkspace Thanks for pointing me in that direction - that is indeed the issue. Looks like ...

DanGamble•6/10/24, 12:03 PM

Is there any issue where this is being tracked yet?

DaniFoldi•6/10/24, 12:26 PM

There 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)

alexandernst•6/10/24, 12:29 PM

I'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?

Aalexandernst I'm reading Pages' docs and I can't find a way to make the server return a prope...

Erisa•6/10/24, 12:37 PM

the status code of

/404

/404

itself should be 200 since its a file that exists (this is confusing but makes sense from a technical standpoint), but having that file present will cause invalid files like

/asdfg

/asdfg

to return 404 - is that not what you are seeing?

alexandernst•6/10/24, 12:38 PM

oh, I thought

/asdf

/asdf

would also return 200 (because of the presence of the 404.html)

alexandernst•6/10/24, 12:38 PM

let me check

Erisa•6/10/24, 12:39 PM

It shouldnt

Erisa•6/10/24, 12:39 PM

https://erisa.uk/asdf for example

alexandernst•6/10/24, 12:45 PM

oh it does!! (I just tried with my page)

alexandernst•6/10/24, 12:45 PM

thank you

Erisa•6/10/24, 1:22 PM

What error do you get?

DDefiDebauchery I manually Purged the CloudFlare cache for one domain and that works. We have Pa...

Chaika•6/10/24, 1:57 PM

Pages doesn't flush cache at all on your custom domains for you

Chaika•6/10/24, 1:58 PM

It's recommended you disable it with a cache rule if you're having issues with it

Chaika•6/10/24, 1:59 PM

possible 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

Chaika•6/10/24, 2:01 PM

yea, 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

Chaika•6/10/24, 2:02 PM

Default 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

Chaika•6/10/24, 2:03 PM

no, 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)

DDefiDebauchery For clarity, you mean setting an app rule to disable caching of the main page? W...

Chaika•6/10/24, 2:13 PM

Your 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

Got an update to this. My original build had ~2500 files and everything was uploaded successfully th

Similar Threads

Similar Threads

Similar Threads