cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1555
Views
0
Helpful
4
Replies
Highlighted
Beginner

WebEx Teams Links with internal TLDs

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!

4 REPLIES 4
Highlighted

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.

Highlighted

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

 

 

  1. https://example.company.i
  2. https://example.company.in
  3. https://example.company.int
  4. https://example.company.inte
  5. https://example.company.inter
  6. https://example.company.intern
  7. https://example.company.interna
  8. https://example.company.internal

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

Highlighted

Hi Thomas!

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

Highlighted

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.





LinkTesting.PNG

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