Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-24665

Add ability to create links using non-standard protocols

XMLWordPrintable

    • 3

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      As a Confluence user, I would like to be able to insert links with custom url protocols.
      The new editor does not properly create links that do not use one of the standard web protocols when inserting with the Insert Link dialog (e.g. http://, ftp://). It creates the <a> but without a href attribute. In 3.5 and earlier, you could create a link for any protocol type using wiki markup: [something://mysite.com]. Inserting the wiki markup results in the link being stripped and the URI appearing as plaintext.

      The only workaround is to insert a link manually with the HTML macro, but not all sites will be able to enable this macro for security reasons.

      Why is this important

      Companies may rely on links for specific tools used by their departments and the ability to link those does impact productivity and ease of use of the platforms

            [CONFCLOUD-24665] Add ability to create links using non-standard protocols

            Deleted Account (Inactive) added a comment -

            Agree with Adrian and Austin!

            Deleted Account (Inactive) added a comment - Agree with Adrian and Austin!

            Austin Sasko added a comment -

            I agree with the above comments, the root issue is still open. I lack the understanding of why ssh:// links and similar protocols were blocked in the first place; however, would like to at least be able to see a ticket in the works that this may be fixed some day.

            Austin Sasko added a comment - I agree with the above comments, the root issue is still open. I lack the understanding of why ssh:// links and similar protocols were blocked in the first place; however, would like to at least be able to see a ticket in the works that this may be fixed some day.

            Adrian Föder added a comment -

            This topic needs to be reopened! since it does not resove the initial problem: There is still no ability to add links to non-standard protocols.

             At least don't mark it as resolved!? please. It is not resolve. Make it Won't fix at least.

            Also please link the issue correctly, maybe to CONF-28103 but that is wrong since we're on CONFCLOUD here.

            In other note it is very annoying that this does not work at all yet. Frustrating for such an expensive tool.

            Adrian Föder added a comment - This topic needs to be reopened! since it does not resove the initial problem : There is still no ability to add links to non-standard protocols .  At least don't mark it as resolved!? please. It is not resolve. Make it Won't fix at least. Also please link the issue correctly, maybe to CONF-28103 but that is wrong since we're on CONFCLOUD here. In other note it is very annoying that this does not work at all yet. Frustrating for such an expensive tool.

            Sam Hasler added a comment -

            Duplicate of CONF-14393?

            Sam Hasler added a comment - Duplicate of CONF-14393 ?

            Bill Cowden added a comment -

            Were any of the 3.5.x version affected by this issue?

            Bill Cowden added a comment - Were any of the 3.5.x version affected by this issue?

            Bill Cowden added a comment -

            Thanks, Steve. I'll add my comments to CONF-28103.

            Bill Cowden added a comment - Thanks, Steve. I'll add my comments to CONF-28103 .

            Steve Lancashire (Inactive) added a comment -

            Hi Bill,
            There has been some discussion here about how best to handle this. Sorry that this has not yet been communicated. We won't ever be able to support all schemes, as some schemes provide security risks, which is the reason for this filtering in the first place. I've opened CONF-28103 to track the bug you've raised with the implementation of this improvement.

            Steve

            Steve Lancashire (Inactive) added a comment - Hi Bill, There has been some discussion here about how best to handle this. Sorry that this has not yet been communicated. We won't ever be able to support all schemes, as some schemes provide security risks, which is the reason for this filtering in the first place. I've opened CONF-28103 to track the bug you've raised with the implementation of this improvement. Steve

            Bill Cowden added a comment -

            Steve Lancashire: is this a closed/dead issue? Clearly there are customers who need this restriction removed from Confluence, and Lamar's comment indicates the product does not honor valid URI scheme syntax. Does the user community have any leverage in this matter or do we need to look at other wiki engines?

            Bill Cowden added a comment - Steve Lancashire: is this a closed/dead issue? Clearly there are customers who need this restriction removed from Confluence, and Lamar's comment indicates the product does not honor valid URI scheme syntax. Does the user community have any leverage in this matter or do we need to look at other wiki engines?

            Lamar Goddard added a comment -

            I agree with Atte. We also would like to use itms-services links. In my opinion Confluence should support all valid URIs. Here's the link to the RFC for URI general syntax:

            http://tools.ietf.org/html/rfc3986#section-3.1

            "Scheme names consist of a sequence of characters beginning with a
            letter and followed by any combination of letters, digits, plus
            ("+"), period ("."), or hyphen ("-")."

            Lamar Goddard added a comment - I agree with Atte. We also would like to use itms-services links. In my opinion Confluence should support all valid URIs. Here's the link to the RFC for URI general syntax: http://tools.ietf.org/html/rfc3986#section-3.1 "Scheme names consist of a sequence of characters beginning with a letter and followed by any combination of letters, digits, plus ("+"), period ("."), or hyphen ("-")."

            Atte Oksman added a comment -

            So this is still unresolved and needs to be opened.

            Atte Oksman added a comment - So this is still unresolved and needs to be opened.

              slancashire Steve Lancashire (Inactive)
              2b88bc0d6fb3 Mark Demma
              Votes:
              10 Vote for this issue
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: