-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
Minor
-
Confluence
Issue Summary
This is reproducible on Data Center: NA
Steps to Reproduce
- Run a CQL query with macros and expand - for example
/wiki/rest/api/content/search?limit=50&expand=body.storage,space,version&cql=macro in ("easy-heading-free") and type in (blogpost, page)
- The result will return a pagination cursor. Use the cursor to go to the next and it fails some times - try using a script.
/wiki/rest/api/content/search?next=true&cursor=_f_NTA%3D_sa_WyJcdDIyMDE1Nzg5MyBpJGBLSHI%2BSkVhUEhUQVJXPj8%2BMyBjcCJd&expand=body.storage,space,version&limit=50&start=50&cql=macro in ("easy-heading-free") and type in (blogpost, page)
- An error 400 Bad request is returned from XpSearch Aggregator
Expected Results
Actual pagination results
Actual Results
An exception is returned
{"statusCode":400,"message":"com.atlassian.confluence.api.service.exceptions.SSStatusCodeException: CQL was parsed but the search manager was unable to execute the search. Error message: com.atlassian.confluence.api.service.exceptions.SSStatusCodeException: There was an illegal request passed to XP-Search Aggregator API : HTTP/1.1 400 Bad Request"}
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
No updates yet unfortunately