# Link to a UNC path

**URL:** <https://meta.discourse.org/t/link-to-a-unc-path/64742>\
**Category:** Support\
**Created:** [Juin 19, 2017, 9:20 UTC](https://meta.discourse.org/t/link-to-a-unc-path/64742 "2017-06-19T09:20:15Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [Février 4, 2019, 6:23 UTC](https://meta.discourse.org/t/link-to-a-unc-path/64742/15 "2019-02-04T18:23:40Z")

</div>

It’s weird… `<a href="file://myfile">link</a>` works, but `[link](file://myfile)` does not. But both options work for other custom schemes as @jomaxro said 🤔

Maybe something in the commonmark link internals is stripping out file:// specifically. A quick search doesn’t reveal anything obvious in the discourse codebase.

@user2 the workaround for now is to use the HTML syntax for your link

```plaintext
<a href="file://myfile">link</a>

```

* * *

Edit: even with that, we still have an issue with file:// protocols. It is very common for file paths to start with a `/` (signifying the root of the filesystem), so the link looks like `file:///myfile`. Our sanitizer doesn’t like the three slashes at the beginning, and treats the link as invalid.

---

_[View the full topic](https://meta.discourse.org/t/link-to-a-unc-path/64742)._