Closed Bug 290977 Opened 20 years ago Closed 14 years ago

error or incorrect results on query if querystring > 2083 chars (truncated by using internet explorer)

Categories

(Bugzilla :: Query/Bug List, defect, P4)

2.10
defect

Tracking

()

RESOLVED DUPLICATE of bug 480044

People

(Reporter: alexanderkraus, Unassigned)

References

Details

(Whiteboard: IE chops it)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322) Build Identifier: if you execute advanced search and the resulting querystring ist longer than 2083 chars, internet explorer doesnt submit or receive the searchdata. You can get such a long querystring easily if you have many products. See http://support.microsoft.com/default.aspx?scid=KB;en-us;q208427 for details Reproducible: Always Steps to Reproduce: 1.open advanced search 2.selecting many products 3.submit the query Actual Results: nothing happens if your querystring is longer than 2083 chars Expected Results: executing the query, displaying the expected data
this will be fixed by bug 15809
Depends on: 15809
If this is going to be fixed by bug 15809, why is it not confirmed?
It won't exactly be *fixed* by bug 15809, but it will make it extremely unlikely to happen. However, I'd agree this is a bug, so I'll confirm it.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
Version: unspecified → 2.10
*** Bug 309764 has been marked as a duplicate of this bug. ***
*** Bug 332235 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > this will be fixed by bug 15809 > so we can reject this bug as duplicate of bug 15809 (?)
*** Bug 335488 has been marked as a duplicate of this bug. ***
*** Bug 338799 has been marked as a duplicate of this bug. ***
Hi guys, Does it look like this will be fixed in the next Bugzilla release? If so, do you have any idea when the next release will be? Thanks, Graeme
Do you have an example URL that causes this in IE? I don't get the error in IE with the uber-long URL from bug 281325. But with FF 1.5 and trunk I do get an error, noted in bug 344222 Request-URI Too Large The requested URL's length exceeds the capacity limit for this server. Apache/2.0.52 (Red Hat) Server at bugzilla-test.mozilla.org Port 443
(In reply to comment #10) > Do you have an example URL that causes this in IE? > I don't get the error in IE with the uber-long URL from bug 281325. when you paste the URL into IE, it silently truncates it. in IE the url ends in component=Disability+Access& which is 2047 characters. however if you paste the url into notepad, you'll see it actually ends in &value0-0-0= there are also server-side limits -- the screenshot on bug 281325 is the web server rejecting the request, not firefox.
byron, quite correct, thanks. I was expecting an "error" per the comments and summary, but I got query results.
Summary: error on query if querystring > 2083 chars (using internet explorer) → error or incorrect results on query if querystring > 2083 chars (truncated by using internet explorer)
Whiteboard: IE chops it
*** Bug 345241 has been marked as a duplicate of this bug. ***
for reference, this is worse if you use ms outlook, which doesn't mention that it decided not to send the full link to the browser :).
Here's the relevant Apache limit: httpd-2.2.8/include/httpd.h: #define DEFAULT_LIMIT_REQUEST_LINE 8190 Exceeding this limit produces this message: Request - URI Too Large The requested URL's length exceeds the capacity limit for this erver. Request failed: URI too long
Oops -- typo. Second line of error message should be The requested URL's length exceeds the capacity limit for this server.
This is now less severe, since bug 15809 has been fixed.
Severity: major → normal
Priority: -- → P4
I noticed that this BR has been issued against version 2.10 but at my organization (Intech) we have version 3.0.5 installed, and the problem persists. Was it supposed to be fixed? Same situation: long queries work ok in Mozilla Firefox but keep failing in MS IE.
(In reply to comment #19) > I noticed that this BR has been issued against version 2.10 but at my > organization (Intech) we have version 3.0.5 installed, and the problem > persists. Was it supposed to be fixed? No. Look at the status of the bug.
Fixed in Bugzilla 3.6.5 and 4.0.1.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.