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

REST API pagination (eg, /rest/api/space) returns more data than available

XMLWordPrintable

      Issue Summary

      This issue relates to general paginated results.

      Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Request /rest/api/space to collect all of the spaces available without using ?expand parameter;
      2. Verify that Confluence returns the exact amount of spaces that exist in the instance;
      3. Now add the ?expand parameter, for example:
        1. https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999

      Expected Results

      Using ?expand produces the same array as without it, except that it expands the required fields.

      Actual Results

      Using ?expand causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.

      Workaround

      Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:

      https://ConfluecneBaseURL/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20

      Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

       

      1. Go to a page where you have the Document States Report macro failing
      2. Edit the page
      3. Edit the macro and modify the value of “Number of items to display” and set it to “11”
      4. Save the page
      5. Check if the report is rendered successfully

            [CONFSERVER-95272] REST API pagination (eg, /rest/api/space) returns more data than available

            Niraj Bhawnani made changes -
            Labels Original: blocking-7.19.22 blocking-8.5.9 blocking-8.9.1 ecohelp release-blocker resolved-in-vf sec-escape security security-escape security-imported vuln-ticket-was-closed New: blocking-7.19.22 blocking-8.5.9 blocking-8.9.1 ecohelp release-blocker resolved-in-vf sec-escape security security-imported vuln-ticket-was-closed
            Niraj Bhawnani made changes -
            Labels Original: blocking-7.19.22 blocking-8.5.9 blocking-8.9.1 ecohelp release-blocker resolved-in-vf security security-escape security-imported vuln-ticket-was-closed New: blocking-7.19.22 blocking-8.5.9 blocking-8.9.1 ecohelp release-blocker resolved-in-vf sec-escape security security-escape security-imported vuln-ticket-was-closed
            Edward made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 942341 ]
            Kusal Kithul-Godage made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 936965 ]
            Puventhira Mannen made changes -
            Fix Version/s New: 8.5.11 [ 108690 ]
            Hemant Gupta made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 930024 ]
            Srinatha T made changes -
            Description Original: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://XXXXXXXXXX/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully             		New: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://ConfluecneBaseURL/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully
            Saurabh Bhatia made changes -
            Description Original: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://confluenceBaseURL/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully             		New: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://XXXXXXXXXX/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully
            Srinatha T made changes -
            Description Original: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://confluence.generali.at/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully             		New: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://confluenceBaseURL/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully
            Srinatha T made changes -
            Description Original: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://confluence.generali.at/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has actually provided workaround and it helped lower down the CPU usage. 

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully             		New: h3. Issue Summary

            This issue relates to general paginated results.

            Requesting data from an endpoint such as /rest/api/space or rest/api/content causes Confluence to return more data than available.

            This is reproducible on Data Center: yes
            h3. Steps to Reproduce
             # Request {{/rest/api/space}} to collect all of the spaces available without using {{?expand}} parameter;
             # Verify that Confluence returns the exact amount of spaces that exist in the instance;
             # Now add the {{?expand}} parameter, for example:
             ## [https://fqdn/rest/api/space?expand=description.plain&limit=1&start=999]

            h3. Expected Results

            Using {{?expand}} produces the same array as without it, except that it expands the required fields.
            h3. Actual Results

            Using {{?expand}} causes Confluence to keep returning data past the available amount, which breaks apps that loop through the resulting array.
            h3. Workaround

            Currently there is no known workaround for this behavior. But if you have Comala Document management app and noticed that the REST calls are related to Comala like below:
            {code:java}
            https://confluence.generali.at/rest/cw/2/report/search?cql=awphasworkflow%3Dtrue%20AND%20space%20IN%20(%22TE%22)%20AND%20state%20IN%20 {code}
            Then Comala Tech has shared few steps to lower the CPU usage. Basically, number of items to be displayed in the report should be 11 or less. Below are the steps recommended by Comala tech.

             
             # Go to a page where you have the Document States Report macro failing
             # Edit the page
             # Edit the macro and modify the value of “Number of items to display” and set it to “11”
             # Save the page
             # Check if the report is rendered successfully

              24ee36512d14 Sumitra Sahu (Inactive)
              resteves Rodrigo Heinzen
              Affected customers:
              45 This affects my team
              Watchers:
              64 Start watching this issue

                Created:
                Updated:
                Resolved: