To follow up from Compute service caching - #6 by PaulRudin, with a more specific observation.
I’ve determined that the cache behaviour for compute services and VCL services isn’t the same in the presence of an origin response that has a Cache-control header that includes no-store. If there’s also a surrogate-control header then the VCL service will still cache the response according to whatever’s surrogate-control says. But using the fetch api in a compute service, there’s no caching.
It feels a little odd that the passthrough cache behaves differently according to whether it’s a compute or vcl service. There’s not really an indication in the docs that there’s a difference.
I’ve already got a support ticket related to this, but I just thought I’d mention it here in case anyone had any comments.