Blazor WebAssembly 3.2, Dll files are blocking by McAfee Web Gateway

[mihaimyh]

It seems even after renaming .dll to another extension some (corporate) firewalls are still blocking them:

Is there any workaround for this except contacting the corporate admin team which will definitely won't unlock them?

[javiercn]

@mihaimyh thanks for contacting us.

You can try renaming the published output dlls as described here.

Please let us know if that solves your problem or if it still blocks the dlls. If that doesn't fix the problem, you can use a custom boot resource loader as described here where you have full control of the resource loading process.

[mihaimyh]

@javiercn I already renamed dlls like I mentioned initially. If you look closely to the screenshots the Microsoft.AspNetCore.Components.WebAssembly has the extension .myh instead of .dll

[javiercn]

@mihaimyh I missed the rename.

I would try creating a bundle with the file contents and use a custom boot resource loader to download the dlls.

[mihaimyh]

@javiercn I am not sure what do you mean with "custom boot resource", are there any docs for this?

[javiercn]

@mihaimyh you can alter the files in any way that let you get through the proxy, download them ahead of time and implement your own resource loader.

...

<script src="_framework/blazor.webassembly.js" autostart="false"></script>
<script>
  Blazor.start({
    loadBootResource: function (type, name, defaultUri, integrity) {
      console.log(`Loading: '${type}', '${name}', '${defaultUri}', '${integrity}'`);
      switch (type) {
        case 'dotnetjs':
        case 'dotnetwasm':
        case 'dll':
            return await getDllContentsAsResponseObject(name, integrity);
        case 'timezonedata':
          return  `https://my-awesome-cdn.com/blazorwebassembly/3.2.0/${name}`;
      }
    }
  });
</script>