Inconsistent webresources returned in CQL search results

Issue Summary

When using the CQL search API and expanding web resources, inconsistent webresource contents are returned.

Steps to Reproduce

1. Create Page 1 and add an /info macro to it.
2. Create Page 2, but leave it empty.
3. Search with /rest/api/search?cql=title="Page%201"&expand=content.body.export_view.webresource.tags.css,content.body.export_view.webresource.uris.css and observe the results.
4. Search with /rest/api/search?cql=title="Page%202"&expand=content.body.export_view.webresource.tags.css,content.body.export_view.webresource.uris.css and observe the results.
5. Search with /rest/api/search?cql=title%20IN%20("Page%201","Page%202")&expand=content.body.export_view.webresource.tags.css,content.body.export_view.webresource.uris.css and observe the results.
6. Remove the /info macro from Page 1.
7. Add an /info macro to Page 2.
8. Search with /rest/api/search?cql=title%20IN%20("Page%201","Page%202")&expand=content.body.export_view.webresource.tags.css,content.body.export_view.webresource.uris.css and observe the results.

Expected Results

The contents of the webresource section matches the resources required by the pages in the search results.

Actual Results

• When fetching multiple pages at once through the REST API, the webresource expansion of all the returned pages is set to the one of whichever page is the first result, even if the pages require different web resources.
• The “colors” stylesheet is not listed in the “webresource.uris” expansion.
• The “webresource.uris.css” expansion does not work if it contains an empty list.

Workaround

Difficult (visit link below).

See https://community.developer.atlassian.com/t/weird-behaviour-of-body-webresource-expansions/44523.