How to bypass "Cache Everything" through request's Cache-Control directive

Our API responses are currently properly cached (CF-Cache-Status = HIT/MISS), but is there a way to respect client request’s Cache-Control directive when using “Cache Everything”?

This question was quickly closed. I agree about the answer, but is there a way to bypass cache for authenticated API calls (respecting either Authorization or Cache-Control: no-cache headers)?
Using separate URL patterns (/api/authenticated/... vs /api/anonymous) isn’t possible for us.
Could we implement this using workers?

Thanks for the help!

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.