Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 335742

Summary:	[client][search][ie] Global search broken on IE
Product:	[ECD] Orion	Reporter:	John Arthorne <john.arthorne>
Component:	Client	Assignee:	Project Inbox <e4.orion-inbox>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	P3	CC:	mamacdon
Version:	0.2
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description John Arthorne

2011-01-28 17:04:23 EST

I20110128

Search doesn't work on IE. I'm sure this worked in yesterday's build...

For example I go to:

http://localhost:8080/search?q=var

And I get back:

{"responseHeader":{"status":0,"QTime":1,"params":{"wt":"json","fl":"Id,Name,Length,Directory,LastModified,Location","hl":"true","q":"var"}},"response":{"numFound":0,"start":0,"docs":[]},"highlighting":{}}

Doing the same query on FireFox on the same server instance gives a large number of hits.

Comment 1 John Arthorne

2011-01-28 17:19:28 EST

This appears to be a client problem. The request that arrives on the server is:

GET /search

I.e., the query parameter is missing.

Comment 2 John Arthorne

2011-01-28 17:30:06 EST

Actually ignore the previous comment. I'm not sure what's going, but trying to run with latest from master I can't get the client UI to load at all. Giving up on debugging it for now.

Comment 3 John Arthorne

2011-01-28 17:45:48 EST

Grr, this now seems to be working consistently. Maybe I had multiple servers running or something. I will reopen if I see it again.

Comment 4 John Arthorne

2011-01-31 10:51:28 EST

Tested again this morning on a fresh build and all seems good.

Comment 5 Mark Macdonald

2011-01-31 11:15:05 EST

(In reply to comment #4)
> Tested again this morning on a fresh build and all seems good.

Did you try Cache > Clear Browser Cache from IE's Developer Tools at any point while you were seeing this bug? This seems to be the only reliable way to clear IE's cache.

I've had a few nasty surprises where IE's aggressive cache policy caused it to load stale client code. Maybe that was the case here?

Comment 6 John Arthorne

2011-01-31 13:19:48 EST

That could certainly be it. I didn't clear the IE cache at the time.