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

CORS for Specific URLs filter Confluence 7.15+

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • Security
    • None
    • 30
    • 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.

      Previously CORS was able to be configured for specific URLs using filters in the web.xml as noted in CONFSERVER-41269.

      This is no longer possible after the web.xml cleanup that happened as part CONFSRVDEV-21301.

      It would be good to add this functionality back to allow admins to configure CORS filters for specific URLs again.

          Form Name

            [CONFSERVER-80056] CORS for Specific URLs filter Confluence 7.15+

            Michael Andreacchio added a comment -

            Dear Customers,

            Thank you for your patience on this request. We apologise for building out this change to web.xml and not in hand ensuring that our documentation was updated with a viable and easy to execute workaround.
            We've updated both our documentation, and created a KB article explaining how to set up CORS configuration in Confluence for specific URLs, please see the following resources:

            I hope these are able to guide you in fixing this issue from here on. Cheers.

            Michael Andreacchio
            Confluence DC Product Management

            Michael Andreacchio added a comment - Dear Customers, Thank you for your patience on this request. We apologise for building out this change to web.xml and not in hand ensuring that our documentation was updated with a viable and easy to execute workaround. We've updated both our documentation, and created a KB article explaining how to set up CORS configuration in Confluence for specific URLs, please see the following resources: Configuring allowlists - Allow Incoming Configure CORS for specific urls I hope these are able to guide you in fixing this issue from here on. Cheers. Michael Andreacchio Confluence DC Product Management

            Shubham Kumar added a comment -

            Please implement this feature.

            Shubham Kumar added a comment - Please implement this feature.

            drabik added a comment -

            We ended up implementing the API call in the back end, where CORS does not apply.

            drabik added a comment - We ended up implementing the API call in the back end, where CORS does not apply.

            Maximilian Walz added a comment -

            The allowlist in the UI does not work

            Maximilian Walz added a comment - The allowlist in the UI does not work

            lvms added a comment -

            Please add this feature back. This is a regression.

            lvms added a comment - Please add this feature back. This is a regression.

            Martin Poirier added a comment -

            Why is this a suggestion ? this is regression bug, someone did a clean up of the web.xml and forgot this feature.
            This is really impacting for the upgrade.

            Martin Poirier added a comment - Why is this a suggestion ? this is regression bug, someone did a clean up of the web.xml and forgot this feature. This is really impacting for the upgrade.

            Josué Garcia added a comment - - edited

            @Roy Lu I wouldn't bother, the fastest solution is to just migrate to Conflunce Cloud.

            Josué Garcia added a comment - - edited @Roy Lu I wouldn't bother, the fastest solution is to just migrate to Conflunce Cloud.

            Roy Lu added a comment -

            We upgraded our instance today not knowing the CORS feature is completely dropped and now our integrations are broken. It causes a huge headache. Can you please fix it asap? Your Allowlist feature in the UI is never working and now you completely drop the CORS filter workaround in the web.xml file, the last version that supports this is 7.15, which is already a sunset version. It is not acceptable! Please come up with at least a workaround!

            Roy Lu added a comment - We upgraded our instance today not knowing the CORS feature is completely dropped and now our integrations are broken. It causes a huge headache. Can you please fix it asap? Your Allowlist feature in the UI is never working and now you completely drop the CORS filter workaround in the web.xml file, the last version that supports this is 7.15, which is already a sunset version. It is not acceptable! Please come up with at least a workaround!

            Richard J. Rasor added a comment -

            Please implement this feature.

            Richard J. Rasor added a comment - Please implement this feature.

            Razvan Solea added a comment - - edited

            Please implement this feature. Since we migrated our older Confluence to version 7.19 this blocks currently the page views tracking on our confluence instance for the internet facing URL. Also there is a functionality to export the public view as PDF which is also blocked because of this.

            [Later Edit] @Roy Lu: Migrating to Cloud is not an option based on the Corporate policies. While easy, it's not always possible.

            Razvan Solea added a comment - - edited Please implement this feature. Since we migrated our older Confluence to version 7.19 this blocks currently the page views tracking on our confluence instance for the internet facing URL. Also there is a functionality to export the public view as PDF which is also blocked because of this. [Later Edit] @Roy Lu: Migrating to Cloud is not an option based on the Corporate policies. While easy, it's not always possible.

              Unassigned Unassigned
              caronson Cole Aronson
              Votes:
              97 Vote for this issue
              Watchers:
              69 Start watching this issue

                Created:
                Updated:
                Resolved: