topic Re: WebEx Teams Links with internal TLDs in Collaboration Applications

WebEx Teams Links with internal TLDs

itshorty — Mon, 15 Apr 2019 08:32:39 GMT

Hi!

I'm posting this feature request here - hope thats ok!

Following situation: if you post a URL like https://comunity.cisco.com/foo it's automaticaly converted to a clickable link.

If you post a URL to an internal service like https://foo01.company.intern/bar it's not converted an still normal text.

I think every valid URL should be converted to a clickable link.

Thank you!

Re: WebEx Teams Links with internal TLDs

ThomasTh-Frauscher — Tue, 09 Jul 2019 10:51:47 GMT

I am seeing a very similar problem to this (well and this one).

When I try to create links in Markdown formal any that end in .intern are not presented as links but as text.

Re: WebEx Teams Links with internal TLDs

ThomasTh-Frauscher — Tue, 09 Jul 2019 10:58:03 GMT

Looking at the problem in more detail it seems that URLs are expected to end in an 2 or 3 character extension.

Of the above it is only the .in and .int extentions that render as linked URLs. I believe that they all should do so.

Re: WebEx Teams Links with internal TLDs

itshorty — Mon, 13 Jan 2020 17:09:00 GMT

Hi Thomas!

Florian from Frauscher IT here 😉 .in and .int are public known TLDs so the are working as expected.

Re: WebEx Teams Links with internal TLDs

ThomasTh-Frauscher — Mon, 13 Jan 2020 17:28:00 GMT

I did some further tests based on what you said and you are correct. It is not as simple as 2 or 3 chracters get passed.

Based on what you said .co, .at, .uk and .abc must be valid top level domains as must be .abc

Re: WebEx Teams Links with internal TLDs

Joe.Gainey — Thu, 17 Mar 2022 17:27:55 GMT

Confirmed that internal top level domain links do not work when using markdown. this seems very limited but i can understand that there are some security concerns with posting an internal clickable link. if there is a way to allow this it would be helpful.