I am adding progressive web app functionality to an existing web application, and came across a curious edge case. In the scenario, I have implemented some pretty standard caching of API endpoints etc, but bypassing the cache on others. On one of these endpoints I bypass, I am initiating/retrieving a video stream which simply passes through the service worker, except it doesn't work on iOS safari (latest) but works fine going through other browsers on various other devices. It works fine on iOS if I disable the service worker. The error is rather nondescript, but my research so far has led me to believe there could be some potential cross-origin issue going on, or the wrong headers are being formed for some reason. This could be a potential server side thing, which makes life slightly trickier since I don't have access to the content store, which is serviced separately to the main backend. This issue is isolated to video format GET requests, other file types and general API calls all work as expected.
If anyone could advise me or point me to some literature/documentation on how safari+iOS deals with this, I would greatly appreciate it.
