Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-12818

Add a URL encoder tool to help with URLs with special chars

XMLWordPrintable

    • 2
    • 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.

      I had trouble adding links to network folders, with the format file:///\\server\folder\files.doc

      However after using the following site i was able to create correctly encoded URL links
      http://www.blooberry.com/indexdot/html/topics/urlencoding.htm

      So my suggestion is for you to have a built-in encoding tool (simple to program) instead of people having to use external utilities.

            [CONFSERVER-12818] Add a URL encoder tool to help with URLs with special chars

            George Varghese added a comment -
            Atlassian Update - 24 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.

            Kind regards,
            Confluence Data Center

            George Varghese added a comment - Atlassian Update - 24 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues , current work, and future plans. Kind regards, Confluence Data Center

            Harald Mueller added a comment -

            Is there any progress on this?

            Were waiting for a solution on safe encoding for years now.

            My problem https://support.atlassian.com/browse/CSP-100642 had been linked to this request and closed by the promise of implementing this feature. We're using xml in URLs for queries and Confluence is not able to escape this valid code but brakes the function. It should be easy to add safe encoding here.

            Any ideas when?

            Harald Mueller added a comment - Is there any progress on this? Were waiting for a solution on safe encoding for years now. My problem https://support.atlassian.com/browse/CSP-100642 had been linked to this request and closed by the promise of implementing this feature. We're using xml in URLs for queries and Confluence is not able to escape this valid code but brakes the function. It should be easy to add safe encoding here. Any ideas when?

            Intel CHD Jira Admin added a comment -

            I vote strongly for a solution here! We just had a problem with "unsafe" characters in a URL, which Confluence silently rejects in a user-unfriendly way (see https://support.atlassian.com/browse/CSP-90374). My suggestions:

            1. Spot unsafe URLs when they are entered and report the real problem to the user. See the support case cited above for the current behavior.
            2. Propose a safe encoding to the user.
            3. If the user rejects the proposed encoding, do not treat the link text as a link (perhaps just use the text as plain text in the page). Again see the support case for the current behavior.

            Intel CHD Jira Admin added a comment - I vote strongly for a solution here! We just had a problem with "unsafe" characters in a URL, which Confluence silently rejects in a user-unfriendly way (see https://support.atlassian.com/browse/CSP-90374 ). My suggestions: Spot unsafe URLs when they are entered and report the real problem to the user. See the support case cited above for the current behavior. Propose a safe encoding to the user. If the user rejects the proposed encoding, do not treat the link text as a link (perhaps just use the text as plain text in the page). Again see the support case for the current behavior.

              Unassigned Unassigned
              2f398ae07828 Adam Bosna
              Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: