• 3
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      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.

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

            We're in 2022 and still no winscp-sftp:// or sftp:// because the vendor thinks they know better than the system owners.

            Christopher Martin added a comment - We're in 2022 and still no winscp-sftp:// or sftp:// because the vendor thinks they know better than the system owners.

            Hi Steven Lancashire,

             

            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.

            This should be decided by the admin, not by the vendor.

            Sebastian Mendel added a comment - Hi Steven Lancashire,   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. This should be decided by the admin, not by the vendor.

            Sam Hasler added a comment -

            Duplicate of CONF-14393?

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

            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?

            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 .

            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

            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?

            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 ("-")."

            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.

            Unfortunately Bill there still are some restrictions in the protocol.

            We only allow alphabetic characters in the protocol, so since your protocol has a hyphen it will not pass our security filter.

            Steve Lancashire (Inactive) added a comment - Unfortunately Bill there still are some restrictions in the protocol. We only allow alphabetic characters in the protocol, so since your protocol has a hyphen it will not pass our security filter.

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

                Created:
                Updated:
                Resolved: