Actions
Feature proposal #7261
closed
Improve userlist searching behavior to use GET when possible
Description
GET provides better SEO in regards to back navigation and URL sharing. POST prevents both. The problem is if the user has too many fields then GET will fail since search criteria will be cut off. Either make this a parameter or do a rough estimate based off the search criteria available to see if the URL could be too long.
Updated by krileon over 5 years ago
Best option is for it to always be a POST, but also support GET (already the case). After the POST has been processed do a redirect to the userlist URL with the search criteria, but only the criteria specifically being used as a form GET request would include even empty inputs which we don't want.
Updated by krileon over 5 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Implemented in MR !1400
Updated by
Actions