Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-899

Ability to access additional response headers when using requestJira

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

      When you use the fetch() API in the browser, you only get a subset of the response headers because of browser security restrictions known as CORS-safelisted response headers.

      By default, only a small set of headers (like Cache-Control, Content-Language, Content-Type, Expires, Last-Modified, and Pragma) are accessible via response.headers.

      It would be good to add the names of additional headers to the Access-Control-Expose-Headers header of the preflight request in order for the JavaScript code to access those.

      For example the ff:

      Retry-After
      X-Ratelimit-Limit
      X-Ratelimit-Remaining
      X-Ratelimit-Reset

            [ECO-899] Ability to access additional response headers when using requestJira

            A thing to mention: It is not only related to using the fetch API but also to all forge related methods, like "requestJira" from forge bridge.

            Jona Ittermann [Decadis AG] added a comment - A thing to mention: It is not only related to using the fetch API but also to all forge related methods, like "requestJira" from forge bridge.

            IMHO: Forge should provide developers with the ability to configure which headers are exposed—ideally via manifest settings.

            This would help restore parity with Connect and enable more robust client-side integrations.

            Would it be possible to update the documentation accordingly, especially given that Forge is now the preferred framework and support for Connect is being phased out?

            For reference:
            https://developer.atlassian.com/cloud/jira/platform/rate-limiting/#rate-limit-related-headers

            Thanks so much in advance, and appreciate all your work!

            Cheers !

            Martin Kistner [Decadis AG] added a comment - - edited IMHO: Forge should provide developers with the ability to configure which headers are exposed—ideally via manifest settings. This would help restore parity with Connect and enable more robust client-side integrations. Would it be possible to update the documentation accordingly, especially given that Forge is now the preferred framework and support for Connect is being phased out? For reference: https://developer.atlassian.com/cloud/jira/platform/rate-limiting/#rate-limit-related-headers Thanks so much in advance, and appreciate all your work! Cheers !
            Sherica Ocbania made changes -
            Labels New: ecohelp
            Sherica Ocbania created issue -

              Unassigned Unassigned
              26a024868f5f Sherica Ocbania
              Votes:
              27 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated: