according to the GFM docs:
An extended url autolink will be recognised when one of the schemes
http://,https://, orftp://, followed by a valid domain, an a valid domain must contain at least one period.
So it may be a bug in the spec that GitHub linkifies http://server/user, or it may be a bug in the spec...
Links without dot are accepted as valid for intranets while working inside an organization. Maybe for Internet they must have a dot because of how it was designed, but while working inside companies you can have links without a dot.
I realize the links are valid, I'm just opening a discussion about whether to follow the spec to the letter or deviate from it for "observed compatibility"/"common use", the implication being that other apps that work with/parse GFM may behave differently.
I personally also use intranet links in my Markdown documents, so I would be tempted to "fix" this issue, I just wanted more feedback first. :)
I wonder if anyone has filed an issue against the GFM spec regarding this.
I do not think anyone has filled this issue. Is this their issue tracker? https://github.com/commonmark/CommonMark
The answer should be simple, does the spec for GFM is representing links for internet only or internet and intranets? If it is for both, then, GFM is bugged. If it is for internet only, then, is not a bug, therefore, an enhancement for GFM would be for it to also accept links for intranets too.
Note that you can always force link-highlighting with <>:
<http://server/user>
<https://github.com/>
Most helpful comment
Note that you can always force link-highlighting with
<>: