# Links broken with (at least) two underscores in URL

**URL:** https://meta.discourse.org/t/links-broken-with-at-least-two-underscores-in-url/72976
**Category:** Bug
**Created:** [10월 28, 2017, 2:57오후 UTC](https://meta.discourse.org/t/links-broken-with-at-least-two-underscores-in-url/72976 "2017-10-28T14:57:02Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![Vitaly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/vitaly/32/120475_2.png) [@Vitaly](https://meta.discourse.org/u/Vitaly)
#### Post date: [10월 28, 2017, 11:28오후 UTC](https://meta.discourse.org/t/links-broken-with-at-least-two-underscores-in-url/72976/7 "2017-10-28T23:28:30Z")

</div>

That’s a known issue:

[https://github.com/markdown-it/markdown-it/issues/38](https://github.com/markdown-it/markdown-it/issues/38)

It’s possible to fix, but not easy. Workaround available.

Correct solution is to make linkifier part of tokenizer process. That’s expensive (for example, email lookahead check for every character). Tradeoff is to listen `:` then do look behind for `http(s)`, and lookahead for the rest. That’s not universal, but will cover all real cases:

- http/https links will be parsed with other tokens, with higher priority than emphasis
- everything else will be detected via text scan & regexps (as linkifier works now), probability of collision is very low.

I have no plans to do this, but if anyone wish to implement - see explanation above. Or use `< >` 🙂

---

_[View the full topic](https://meta.discourse.org/t/links-broken-with-at-least-two-underscores-in-url/72976)._