Smart + Regional is a very powerful combination if your goal is to maximise cache hit rate
Smart + Regional is a very powerful combination if your goal is to maximise cache hit rate
cf.worker.upstream_zone to be supported but if it isnt then no"Cache-Control": "no-cache, no-store, no-transform" on my fetch request in a Worker, will that bypass the Cache Rules?
next-on-pages for; it has an api that gets deployed to workers that calls a graphql endpoint. it works fine locally, and using wrangler, but when deployed i get an error ApolloError: Unexpected token '<', "<html><hea"... is not valid JSONhttps://courses.techleaderslaunchpad.com/graphqlawait response.text() says.✘ [ERROR] *** Received signal #11: Segmentation fault: 11
stack:
✘ [ERROR] Error in ProxyController: Error inside ProxyWorker
{
name: 'Error',
message: 'Network connection lost.',
stack: 'Error: Network connection lost.'
}const operation_json = await operation_result.json() as any;
if(operation_json.result === "win") {
const filename = cacheKey.pathname.split("/").pop() ?? "undefined.pdf";
const filename_json = filename.replace(/\.[^/.]+$/, "") + ".json";
const operation_json_str = JSON.stringify(operation_json, null, 2);
const custom_res = new Response(operation_json_str);
const compressedReadableStream = custom_res.body!.pipeThrough(
new CompressionStream('gzip')
);
// ...
}https://courses.techleaderslaunchpad.com/graphqlawait response.text()