Bug 704095 - [TCMS]A warning "Request-URI Too Large" will come out when select too many component in the "Advanced search".
Summary: [TCMS]A warning "Request-URI Too Large" will come out when select too many co...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: TCMS
Classification: Other
Component: Application
Version: 3.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Yuguang Wang
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-12 07:19 UTC by Xin Gao
Modified: 2015-05-27 22:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-18 05:41:06 UTC


Attachments (Terms of Use)
Request-URI Too Large (16.50 KB, image/png)
2011-05-12 07:20 UTC, Xin Gao
no flags Details

Description Xin Gao 2011-05-12 07:19:07 UTC
Description of problem:
A warning "Request-URI Too Large" will come out when select too many component in the "Advanced search".

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

How reproducible:


Steps to Reproduce:
1. Enter into "Advanced search".
2. Select a plan/case/run product, like "Red Hat Enterprise Linux 2.1".
3. Select many plan/case/run components.
4. Click Search Plan/Case/Run.
  
Actual results:
A warning "Request-URI Too Large" came out.

Expected results:
There is no warning. Or maybe should limit the number of search options.

Additional info:
Web browser: Firefox, chrome.
Please refer to attachment "Request-URI Too Large". 
And related to this bug are as follows.
The number of selected component is 412.
And the character number of URL is 8212.

Comment 1 Xin Gao 2011-05-12 07:20:31 UTC
Created attachment 498446 [details]
Request-URI Too Large

Comment 2 Chaobin Tang 2011-05-18 05:41:06 UTC
First, the error "Request-URI Too Large" is a standard error of HTTP, clearly limiting the allowed length of an URI.

Secondly, the implementation could've been able to use POST method to submit the query and will NOT trigger this error. However, it then gives no visible reference for your query, in this case, the link with your queries.

Additionally, let's just assume no usercases in real world that will have that length of URI. On false situation, we will think about fixes.


Note You need to log in before you can comment on or make changes to this bug.