Forum Discussion
How the new Edge will handle file:// URI ?
JeffOwens I just got an update yesterday. They are goig to raise awareness about this issue with the product team soon-ish. Whether or not they will implement anything in regards to this issue is unclear at this point though.
For now the suggestion seems to be to either change all your links, use IE or configure Edge so that it uses IEMode for the entire website you have your file:// links on.
Thanks narutards
For anyone else interested, we changed all our file:// link references to localfile:// and implemented a new protocol handler in the registry.
For example:
localfile://open?data=\\NASORL1\EngData\MAVIS\ProjectTickets\13092\Engineering-Data\Prototype\
Since this issue only applies to our intranet web application that we've developed internally, it was an easy thing to deploy (you might be able to do it via group policy if you're running AD or via an easy EXE to make those if not).
Also, since this is a registry edit, the protocol will be recognized on any browser.
That's our work-around for now.
- Hi Jeff, what keys did you have to set for the protocol handler? Do yuo have any examples of all the keys you had to set to make this work.
- Eric_Lawrence
Microsoft
Rheinrich21 - https://techcommunity.microsoft.com/t5/discussions/how-the-new-edge-will-handle-file-uri/m-p/2182012/highlight/true#M44645 has a full implementation of an Application Protocol Handler. Basically, you just need the URL Protocol subkey and a Shell\Open\Command value.
But to reiterate the earlier point, you have to very carefully consider the security implications of this approach.
