Fetch inside worker not caching url, when the url is another worker form another account.

I have a worker A, which is running in separate account which returns a static file on GET request with proper cache control headers for caching. This worker A acts like a origin. Now when i do a fetch from a worker B, which is running in another account , the fetch is not caching the url response from worker A. Since i have set proper cache control, worker B should consider worker A like any other origin and cache it right ?. Am i missing something ?
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?