Description of problem: The newer pageable JSON collection resources (for example /systems/<fqdn>/activity/, see [1]) will normally return all items in the collection if no page_size= parameter is given. The JSON collections enforce a limit on the number of items returned: if the response would contain more than 500 items, and no page_size= parameter is given, then the request is redirected to add a page_size=20 parameter, to prevent clients from unwittingly getting back a very large response body. However when the redirection happens it is discarding all other query parameters. Therefore if you visit a collection with a filter applied (q= parameter) but no page_size= parameter, you will be redirected to page_size=20 with the filter discarded. [1] https://beaker-project.org/docs-release-19/server-api/http.html#pageable-json-collections Version-Release number of selected component (if applicable): 19.2 Steps to Reproduce: 1. Request a JSON collection with more than 500 items, using a q= parameter to filter but no page_size= parameter. For example, any Beaker system that is a few years old will typically have several thousand activity rows with the Service value of "Scheduler". https://$BEAKER/systems/$FQDN/activity/?q=service:Scheduler Actual results: Redirected to the URL: https://$BEAKER/systems/$FQDN/activity/?q=page_size=20 Filter is discarded. Expected results: Should be redirected to the URL: https://$BEAKER/systems/$FQDN/activity/?q=service:Scheduler&page_size=20 showing the first 20 activity records with service Scheduler.
This doesn't affect anything in Beaker's web UI since the Backgrids always send pagination params.
http://gerrit.beaker-project.org/3993
Beaker 19.3 has been released.