@dani_coll we are also exploring the option to catch the fetch requests instread:
// sw.js
self.addEventListener('fetch', (event) => {
const url = new URL(event.request.url);
// Example: reroute Mapbox requests through your backend
const mapboxHosts = ['api.mapbox.com', 'events.mapbox.com', 'tiles.mapbox.com'];
if (mapboxHosts.includes(url.hostname)) {
const proxy = new URL('/proxy', self.location.origin);
proxy.searchParams.set('u', event.request.url); // original URL encoded
event.respondWith(fetch(proxy, {
method: event.request.method,
headers: event.request.headers,
body: event.request.method !== 'GET' && event.request.method !== 'HEAD'
? event.request.blob()
: undefined,
// credentials behavior mirrors the original by default
}));
return;
}
// Default pass-through
event.respondWith(fetch(event.request));
});
However we could not get this to work. We are trying to implement a service worker in an appengine app. We are having problems with including a service worker javascript implementation with the app bundle at the same directory level as is the compiled main.js file. What we have achieved is service worker javascript deployment in the assets subdirectory. This is not sufficient since the service worker is not able to intercept certain events from main.js when deployed in a subdirectory - to intercept them the implementation of the service worker must be in the same directory as main.js. How can we configure the app build so that it includes a javascript file in the same directory as main.js in the final deployment structure?
Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner
