< class="prominent-subhead ">

Hyperlink which points to the file on a local server does not work in Chrome, "Not allowed to load local resource" error appears

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


When using hyperlinks in a list view which points to a local file server share, it works in Internet Explorer but not in Chrome.


A hyperlink which points to the file on a local server and uses a UNC path, works in Internet Explorer, but not in Chrome.

When you try to open this hyperlink in Internet Explorer, you see that it tries to open the UNC path "\\servername\foldername\filename" and it works.
In Chrome, the address has a different structure: "file://servername/foldername/filename" and when attempting to open it you will receive the following error:

"Not allowed to load local resource: <URL>"


This issue is caused by the Chrome browser's security feature and this cannot be fixed from the K2 side. We cannot control how different browsers handle these types of links. Chrome does this to rule out the possibility of running harmful executables locally.

A solution for this problem is to either run chrome.exe adding this parameter: --allow-file-access-from-files or to use an alternate file sharing approach (e.g. some web service or SharePoint).
The simplest fix will be to map the files to a virtual directory in IIS so that you can then create real HTTP links to the files instead of using file shares, with which it is not possible to control how the browsers handle them.