Bug 599180

Summary: bugzilla can't handle the length of my component lists
Product: [Community] Bugzilla Reporter: Cameron Meadors <cmeadors>
Component: Query/Bug ListAssignee: Simon Green <sgreen>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: low    
Version: develCC: cward, ebaak, sgreen
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-10 00:42:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 631001    

Description Cameron Meadors 2010-06-02 19:36:47 UTC
Description of problem:

When trying to remember a search for bugs based on my groups component list, I get 

414 Request-URI is too long


Version-Release number of selected component (if applicable):


How reproducible:
Everytime I use the list of components for my qe group and try to remember that search


Steps to Reproduce:
1. search for a list of bugs
2. use the component list as part of the search
3.
  
Actual results:

414 error

Expected results:

saves the search

Additional info:

I also get similar error when I click on links from ACK viewer.  those are Referrer URL too long errors.  But it all has to do with the list of components that I use all the time is just too long.

Comment 1 Cameron Meadors 2010-06-03 14:44:42 UTC
This is blocking my ability to report testing status.

Comment 2 Chris Ward 2010-06-04 12:03:35 UTC
This won't be fixed as far as I know. I've tried. :( Frustrating but true. 

I've sent you an example xml-rpc script you can use to pull the numbers. XML-RPC apparently doesn't have any problem with long lists.

Try it with the script i sent to make sure it works.

Comment 3 David Lawrence 2010-06-04 14:33:35 UTC
Unfortunately the apache server configuration is set and we are not able to raise the length value. As Chris mentioned since the XMLRPC API uses POST you are not limited to any length and should work fine. We will need to figure out ways to make Bugzilla better use POST methods in areas where the URI could be rather long. Currently query.cgi uses GET to allow bookmarking of searches as well as saving of searches in the database. We will need to work with the upstream on this as it is the standard behaviour with the upstream code as well.

Dave

Comment 5 Simon Green 2012-05-10 00:42:25 UTC

*** This bug has been marked as a duplicate of bug 820079 ***