`cacheTtlByStatus` is ent? I thought it was for everyone? 🤔

EErisa `cache-control: no-store` should do the trick

D

dave•12/29/23, 12:57 AM

just confirmed, Backblaze B2 returns

Cache-Control: max-age=0, no-cache, no-store

Cache-Control: max-age=0, no-cache, no-store

Cache-Control: max-age=0, no-cache, no-store

Cache-Control: max-age=0, no-cache, no-store

when it's a 403 (missing file)

JJames `cacheTtlByStatus` is ent? I thought it was for everyone? 🤔

J

JamesOP•12/29/23, 12:59 AM

https://developers.cloudflare.com/workers/runtime-apis/request/#incomingrequestcfproperties doesn't mention this, but https://developers.cloudflare.com/cache/how-to/configure-cache-status-code/ kinda does in the first sentence. But then goes on to talk about free limits too. interesting

Ddave just confirmed, Backblaze B2 returns `Cache-Control: max-age=0, no-cache, no-st...

E

Erisa•12/29/23, 1:00 AM

You can do it with page rules. I had thought there was an equivalent in cache rules but I checked and can't find it so...
It feels wrong to write a page rule for a hostname thats not on the zone but I'm 99% sure it works

EErisa You can do it with page rules. I had thought there was an equivalent in cache ru...

D

dave•12/29/23, 1:01 AM

I think it's under cache key?

E

Erisa•12/29/23, 1:02 AM

Oh, duh, its been modernised

E

Erisa•12/29/23, 1:02 AM

Thanks

U

Unsmart•12/29/23, 1:02 AM

Cache key is ent only isn’t it

UUnsmart Cache key is ent only isn’t it

D

dave•12/29/23, 1:02 AM

lemme confirm on my non-enter CF account

UUnsmart Cache key is ent only isn’t it

E

Erisa•12/29/23, 1:03 AM

On free plan you get some options, just limited:

E

Erisa•12/29/23, 1:03 AM

D

dave•12/29/23, 1:03 AM

dang it I got ninja'd

U

Unsmart•12/29/23, 1:03 AM

Interesting

E

Erisa•12/29/23, 1:04 AM

You need ent for the rest

E

Erisa•12/29/23, 1:04 AM

like specific headers, specific query params, etc.

U

Unsmart•12/29/23, 1:04 AM

Ah this is what I was thinking of

C

Chaika•12/29/23, 1:04 AM

you get query string sorting and origin passthrough for free via cache rules

C

Chaika•12/29/23, 1:04 AM

nice guy cf giving ent stuff lol

UUnsmart Ah this is what I was thinking of

E

Erisa•12/29/23, 1:05 AM

Yuh, the cache rules stuff is basically a pretty UI for those custom cache keys. If you want to go crazy and write a string yourself you can do that in a worker (though its a lot easier to get it wrong and mess up your cache)

D

dave•12/29/23, 1:05 AM

D

dave•12/29/23, 1:05 AM

does this look sane if I want to cache all S3 API requests?

CChaika you get query string sorting and origin passthrough for free via cache rules

E

Erisa•12/29/23, 1:06 AM

And True-Client-IP with transform rules

Ddave Click to see attachment

E

Erisa•12/29/23, 1:06 AM

lgtm

E

Erisa•12/29/23, 1:07 AM

Outbound fetch requests go through cache rules and page rules, it feels weird to write them for external hosts but its powerful

CChaika you get query string sorting and origin passthrough for free via cache rules

D

dave•12/29/23, 1:07 AM

you get status code ttl caching too lol

C

Chaika•12/29/23, 1:08 AM

huh I didn't even realize that was an ent thing

D

dave•12/29/23, 1:08 AM

this confuses me, which one takes priority?

D

dave•12/29/23, 1:08 AM

will it use cache-control if present, and if not, the status code ttl?

U

Unsmart•12/29/23, 1:09 AM

I think you need the last option

U

Unsmart•12/29/23, 1:09 AM

Although I guess that would be the input right under that’s very confusing

E

Erisa•12/29/23, 1:10 AM

I'm pretty sure status code TTL is an override, using it instead of "use this TTL" is a tad redundant

EErisa I'm pretty sure status code TTL is an override, using it instead of "use this TT...

D

dave•12/29/23, 1:10 AM

I don't want to override non-200s though

Ddave I don't want to override non-200s though

E

Erisa•12/29/23, 1:10 AM

https://up.erisa.uk/firefox_8oxmdgOT2s.png

E

Erisa•12/29/23, 1:11 AM

I think they would have the same effect, this one just makes more sense in my mind

E

Erisa•12/29/23, 1:12 AM

(note that due to the cache-control spec being super weird you have to do no-store and should not pick no-cache)

EErisa (note that due to the cache-control spec being super weird you have to do no-sto...

D

dave•12/29/23, 1:12 AM

yeah that threw me off earlier today too

EErisa https://up.erisa.uk/firefox_8oxmdgOT2s.png

D

dave•12/29/23, 1:14 AM

Ddave what on earth, Backblaze returns a 403 when it can't find a file

D

dave•12/29/23, 1:16 AM

ah, this is probably because I only gave the B2/S3 API key permissions to read and write files, not list files.

Ddave Click to see attachment

E

Erisa•12/29/23, 1:18 AM

Nice, though we dont cache any 1xx by default and I'm pretty sure the TTL override at the top only applies to 200 :P
Either way, good to be explicit like that and its more clear in future what this rule is doing and can be easily adjusted if needed!

D

dave•12/29/23, 1:19 AM

also did this to avoid caching versioned presigned URLs.

E

Erisa•12/29/23, 1:20 AM

Fancy

EErisa Click to see attachment

D

dave•12/29/23, 1:20 AM

is this the same as toggling

no query parameters

no query parameters

no query parameters

no query parameters?

E

Erisa•12/29/23, 1:23 AM

Yes

E

Erisa•12/29/23, 1:23 AM

The top option is that setting off, the bottom is it on, the ones in the middle are fun ent bonuses

D

dave•12/29/23, 1:23 AM

hmm, it doesn't seem to be working :/

D

dave•12/29/23, 1:23 AM

oh wait

D

dave•12/29/23, 1:24 AM

yep, it's working!

D

dave•12/29/23, 1:24 AM

ty!

D

dave•12/29/23, 1:25 AM

How can I lock this down to only cache for my Worker subrequests?

D

dave•12/29/23, 1:28 AM

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId") and cf.worker.upstream_zone in {"aimoda.workers.dev" "ai.moda"}

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId") and cf.worker.upstream_zone in {"aimoda.workers.dev" "ai.moda"}

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId") and cf.worker.upstream_zone in {"aimoda.workers.dev" "ai.moda"}

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId") and cf.worker.upstream_zone in {"aimoda.workers.dev" "ai.moda"}

Can't do this

D

dave•12/29/23, 1:30 AM

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId" and any(http.request.headers["cf-worker"][*] in {"ai.moda" "aimoda.workers.dev"}))

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId" and any(http.request.headers["cf-worker"][*] in {"ai.moda" "aimoda.workers.dev"}))

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId" and any(http.request.headers["cf-worker"][*] in {"ai.moda" "aimoda.workers.dev"}))

(http.request.uri.query contains "X-Amz-Algorithm=AWS4-HMAC-SHA256" and not http.request.uri.query contains "versionId" and any(http.request.headers["cf-worker"][*] in {"ai.moda" "aimoda.workers.dev"}))

`cacheTtlByStatus` is ent? I thought it was for everyone? 🤔

Similar Threads