Attachment file extension filter and pagination parameters are dropped during space key-to-alias redirect

XMLWordPrintable

    • 1
    • Minor

      Issue Summary

      When a Confluence space has a canonical key that differs from its public alias (e.g., canonical key = KEY-A, public alias = KEY-B), the attachments page generates filter forms and pagination links using the canonical key. However, Confluence enforces a redirect to the public alias URL. During this redirect, parameters such as extensions (file type filter) and pagination cursors are stripped, making it impossible to filter or paginate attachments.

      The redirect occurs regardless of which key is used in the URL — using either the canonical key or the public alias ultimately resolves to the alias URL, and filter/pagination parameters are lost in the process.

      Steps to Reproduce

      1. Identify or set up a Confluence space where the canonical space key differs from the public alias (i.e., the key shown in the URL is not the same as the internal key used by Confluence)
      1. Navigate to the Attachments page of any page within that space
      1. Apply a file type filter (e.g., filter by PNG)
      1. Observe the URL — note that the filter link uses the canonical key rather than the public alias
      1. Click the filter or click Next to paginate

      Expected Results

      • The redirect from the canonical key to the public alias should preserve all query parameters, including extensions (file type filter) and pagination parameters (e.g., cursor, page)
      • Filtering and pagination on the attachments page should function correctly regardless of whether the space has a key/alias mismatch

      Actual Results

      • When the filter or pagination link is clicked, Confluence redirects from the canonical key URL to the public alias URL.
      • During the redirect, filter and pagination query parameters are dropped.
      • As a result, the attachments page reloads without the applied filter and resets to the first page{}

      Workaround

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

              Assignee:
              Unassigned
              Reporter:
              Sameera K
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: