Bug 1043325 - https://hardware.redhat.com/&quicksearch= results in 502 proxy error
Summary: https://hardware.redhat.com/&quicksearch= results in 502 proxy error
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Hardware Catalog
Version: 5.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Tony Fu
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1040296
TreeView+ depends on / blocked
 
Reported: 2013-12-15 23:53 UTC by Tony Fu
Modified: 2014-01-09 06:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-09 06:59:19 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tony Fu 2013-12-15 23:53:58 UTC 
Description of problem:


In a search only includes a quicksearch and the keyword of quicksearch is empty, the search result will includes all certs.  It may cause a proxy error since returning all certs may take more time than the time out setting in server.

Instead, we should return an empty list if the quickserch is the only search and its keyword is empty.

How reproducible:


Steps to Reproduce:
1.Go to https://hardware.redhat.com/&quicksearch=
or in /index.cgi page, click "SEARCH HARDWARE" button without input any keyword in its field
2.
3.

Actual results:
proxy error

Expected results:
an empty list


Additional info:
Comment 1 Tony Fu 2013-12-15 23:59:50 UTC 
patch for review
https://code.engineering.redhat.com/gerrit/17449
Comment 2 Damian Jansen 2013-12-16 00:38:48 UTC 
Ideally, the best fix for this is to return a portion of the results from the database (e.g. "select $query between $pageStart and $pageEnd") for pagination, rather than "select all and filter".
This would then not be a problem, considering the user can also enter * as a search term.
Comment 3 Tony Fu 2013-12-20 07:27:25 UTC 
verified on partner.
Comment 4 Tony Fu 2014-01-09 06:59:19 UTC 
verified on live.
Note You need to log in before you can comment on or make changes to this bug.