Is it intentional that I can't set Cache-Control headers on cachedEventHandler?

[niklas-may]

When you use the cachedEventHandler function, Cache-Control headers are automatically set on the response based on the handler's options object. See here. Setting these headers will make other entities cache the response accordingly—for example, CDNs or browsers.

But in my scenario, I only want nitro to cache the response. But every other part should treat this response as dynamic/private.

This handler...

const options = {
  swr: true, 
  maxAge: 10,
}
cachedEventHandler(async () => await callExternalAp(), options);

... will result in these headers.

Cache-Control: s-maxage=10, stale-while-revalidate

Overriding the headers explicitly is, unfortunately, not possible.

// This has no effect
setResponseHeader(event,"Cache-Control",  "private, max-age=0");

Is this behavior intentional and I am missing some cache-control knowledge, or is this a bug?
I am very happy to get any insights.