Closed Bug 25268 Opened 25 years ago Closed 24 years ago

Using IE and a bad keyword in a query causes server error

Categories

(Bugzilla :: Bugzilla-General, defect, P3)

Product:
Bugzilla
Component:
Bugzilla-General
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED WORKSFORME

People

(Reporter: terry, Assigned: justdave)

Details

Gotta be more careful and check if we're doing the "server-push" hack when
generating an error message.
Status: NEW → ASSIGNED
Priority: P3 → P1
tara@tequilarista.org is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)
Assignee: terry → tara
Status: ASSIGNED → NEW
Chris--I'm very sorry to make you use IE...

:)
Assignee: tara → cyeh
Terry...

I have no idea what you meant in your comment about this bug. Could you please 
elaborate? Thanks.
Status: NEW → ASSIGNED
So, if you are running IE, and you do a query for a keyword, and you type in a
non-existant keyword, then it incorrectly emits the error message.  This is
because the code is designed to work in server-push mode, and disgustingly
hacked to work in non-server-push mode (which is the only thing IE supports).

server-push is the stuff that lets it display "Please stand by..." while working
on the request.
pushing the priority down.
i'm using IE 5.0, and I don't get this error, so I'm guessing MSFT fixed this at 
some point.
OS: Linux → Windows NT
Priority: P1 → P3
i can't get this to happen with IE4 either. i am deciding to not care about IE3.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
We all should be using Mozilla by now. Marking as verified.
Status: RESOLVED → VERIFIED
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: Chris.Yeh → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
QA Contact: matty
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.