@selimgoksu You are correct, it is the computer that has WebReports loaded in the browser that needs internet access, not the WebReports server itself, which makes this normally not a big deal.
The solution is based upon the concept used for the “Parameterized Fixlet Library” and Parameterized Fixlets.
When you actually use the session relevance within a WebReport or Dashboard, it looks like this:
Which would replace
<script src="https://cdnjs.cloudflare.com/ajax/libs/d3/3.5.17/d3.js" integrity="sha256-gfQwA6PlkZsLqWu4bU4hXPrbTqzixm0B5MdvBLI+Oas=" crossorigin="anonymous"></script> in my existing dashboards.
When the WebReport or Dashboard is loaded, the
The added benefit of this approach is that it should cause the browser to render the Dashboard/WebReport faster.
The same concept should apply to CSS, but with slightly different usage.