Referrer doesn't exist, or provides too little detail when visiting links outside of Atlassian Cloud

XMLWordPrintable

    • 1
    • Jira Software, Jira Service Management, Jira Work Management, Confluence

      Issue Summary

      When visiting a link in Confluence to an external site, the referrer header is cut down to just the base URL of the referred URL. For example:

      https://mysite.atlassian.net/wiki/spaces/~[specific page] becomes https://mysite.atlassian.net/

      When visiting a link in Jira Cloud to an external site (such as from a comment in the issue view), the referrer header doesn't exist.

      Steps to Reproduce

      1. Add a link to a Confluence page or Jira Cloud issue that navigates to an external website
      2. Visit the website, and view the referrer headers

      Expected Results

      • Referrer header to provide exactly where the user came from when visiting an external site
        • Links in the issue view of Jira projects should use the strict-origin Referrer-Policy so that application owners know when users navigated to the application from an Atlassian product.

      Actual Results

      • Depending on the product, the URL is either shortened down to the base URL, or the referrer header doesn't exist.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            James W
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: