Disabling automatic asset caching
# workers-helpm
mercmoods
04/18/2023, 2:30 PMI’m seeing some very confusing cache-api behaviour on a worker of mine. I’ve set cache-control headers on a .css asset to be max-age=0, no-cache, but the worker is still caching the request. I can see this because the age response header is a non-zero value and the cf-cache-status says HIT. Is there any way I can turn off this automatic asset caching/any info of what’s going on under the hood?
s
Skye
04/18/2023, 2:39 PMWorkers always run before caching
Skye
04/18/2023, 2:40 PMI'm guessing the place you're fetching it from in your worker is instead the place the caching is occurring
m
mercmoods
04/18/2023, 2:53 PMThank you for the response! I’ll have a look at that. The source is another CF worker which has been service bound.
s
Skye
04/18/2023, 3:01 PMService bindings run in the same thread, not over http(s), so I'd be surprised if that directly was the cause
m
mercmoods
04/18/2023, 6:41 PMSorry, my previous message is wrong. The fetch is from a static storage service so there are no existing cache headers on the .css asset.
mercmoods
04/19/2023, 1:29 PMI achieved my desired behaviour with this change: I added a cacheTtl: 0 flag to the fetch I make inside my worker. I hope that is an acceptable pattern https://developers.cloudflare.com/workers/runtime-apis/request/#requestinitcfproperties