Bypassing Edgemesh® Client for a Specific Asset

In certain situations, you may encounter third-party resources or assets that you prefer not to be cached. While Edgemesh® Client already includes a comprehensive dynamic exclusion mechanism for non-cacheable third-party scripts, there might be cases where you want to explicitly instruct Edgemesh® Client to bypass caching for a specific asset.

To achieve this, you can append the em-bypass=client search parameter to the URL of the asset. By including this parameter, you inform Edgemesh® Client to skip caching the asset through the Service Worker caching layer. This ensures that the specific asset is fetched directly from the origin server each time, without being stored in the cache.

<script 
  type="application/javascript" 
  src="https://example.com/cors-blocked.js?em-bypass=client">
</script>

By utilizing this technique, you have granular control over caching behavior and can ensure that specific assets are always fetched from the origin server, bypassing the caching mechanism provided by Edgemesh® Client.

It's important to note that bypassing caching should be used judiciously and only when necessary, as caching plays a vital role in optimizing website performance.