Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html/api_guide/chap-red_hat_satellite-api_guide-using_the_red_hat_satellite_api#sect-API_Guide-Using_Extended_Searches Section Number and Name: 5.5. Using Extended Searches Describe the issue: After a change in behaviour when moving from sat 6.8 to 6.9, customer has found that some search terms need to be urlencoded when previously they we not. Suggestions for improvement: Document what parameters need to be url encoded and expand more on coverting search terms from UI to API use. Additional information: Documentation looks similar across sat 6.9, 6.10 and 6.11 so probably valid for all In this specific case a datestring was being used for a comparision and ">" not needs to be urlencoded i.e. "search=%3e1970-01-01"
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team. Thank you.