Description of problem:
The Red Hat's Bugzilla repeatedly reports the 'Request-URI Too Large' HTTP error whenever I try to work with a larger set of components.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Navigate to bugzilla.redhat.com
2. Choose 'Search', 'Advanced search'
3. Choose 'Classification: Fedora', 'Product: Fedora', refresh components,
select all Perl packages (perl*) in the Components list.
5. Try to 'Remember search' or sort the resulting list of bugs.
'Request-URI Too Large' HTTP error.
'Remember search' feature or sorting working.
The web server itself is configured to a specific limit for URI length. We are not able to change that value. We ask people who need to use long queries to either do it via XMLRPC which uses POST so therefore has no limit, or to run it from query.cgi which will not convert to URI if the length is over the limit. Problem with the latter is that you cannot create a bookmark or stored search from the search.
Bugzilla will have to be fixed upstream to allow workarounds for this type of problem as not many installations have as many components as we do.
As for your issue, if you are just searching for components with "perl-*" in the name, then instead of selecting all of the components from the list, you can specify a regex using the boolean charts. Do the rest of your query the same way except for the component portion, enter in the boolean charts section at the bottom:
"Component" "regexp" "^perl-"
and that will do the same thing.
Dave, thank you for the explanation. The RE search solves it for me.
As part of the recent Bugzilla 2.4 upgrade the Bugzilla team are cleaning up bugs opened against old versions of Bugzilla. This bug has been flagged as an old bug and will be CLOSED WONTFIX in 7 days time.
If you believe this bug is an issue in the latest Bugzilla version please comment on this bug within 7 days. Doing so will ensure this bug is not closed automatically.
Thanks, the Bugzilla team.
Although I don't get hit by this, it still keeps happening.
*** This bug has been marked as a duplicate of bug 820079 ***