Apr 05 2022 07:27 PM
Apr 05 2022 07:27 PM
I am experiencing an undocumented behaviour when using MS Edge with IntranetFileLinksEnabled group policy.
Our SPA displays anchors with file URL e.g.
<a class="link-text" href="file://shares.domain.com/Share1/fs1/case1/README.txt.summary" rel="noopener noreferrer" target="_blank"> <span data-cy="search-result-path">Share1/fs1/case1/README.txt.summary</span> </a>
Without IntranetFileLinksEnabled enabled, we get the expected error message displayed in the console i.e. Not allowed to load local resource...
When enabled, instead of opening the parent directory and selecting the file as stated in the policy description, the browser is loading the file URL into the browser address bar with the error message Access to the file was denied as shown:
Refreshing the page opens the file.
The file is also accessible to the user via File Explorer with the file URL
Have verified the following:
Have tried the following:
Would appreciate any suggestions to achieve the desired behaviour of opening the parent directory in File Explorer and selecting the file item.
Apr 13 2022 06:11 AM - edited Apr 13 2022 06:13 AM
Just had the same problem. For me the issue was that the file was blocked, as seen in the properties of the file at the bottom of the general tab:
This File Came From Another Computer and Might Be Blocked
Once "allowed" the link in Edge behaves as expected. It seems this protection setting gets checked even though Edge won't directly launch the file.
Edit: Reading your question again, it seems to be a different problem since a reload wouldn't open the file in my case.
Apr 13 2022 04:26 PM
Apr 13 2022 11:58 PM
Jun 27 2022 11:58 PM
After a bit of a hiatus, I revisited this issue and managed to get it work.
I got it to work by using a "PlainHostName" as the file URL's hostname. Instead of file://shares.domain.com/folder/myfile.docx, the URL that worked was file://shares/folder/myfile.docx.
For some reason, direct mapping wasn't working. I previously had added to Local Intranet Zone the following without success: