LQ Search result links cannot be found
 

Is it just me or is anyone else having trouble visiting the links produced by a search?

I've tried a couple of different searches this afternoon and when I attempt to jump to the forum thread listed in the search results, I get an error message telling that the page cannot be found.

It's not just a few of the links, none of the ones I've tried have worked; even fairly recent entries.

Servers having trouble? Should I try back later?

The couple searches I tried look ok. What was the exact search(es) you ran and what was the exact error message?

--jeremy

OK... I was trying to search for "Tk/Tcl" and I suspect that the CGI is having trouble with that "/" in the passed string.

I'd bet that search for "/dev/null" would cause a similar "404". Let's see... Yep. The slash seems to break the CGI.

A search for Tk/Tcl works as expected for me. What browser/OS are you using?

--jeremy

The search itself works. It's the links in the returned list that fail when they're clicked on. I get a 404 error. If you'd like the exact text, I can post it tomorrow.

Firefox 2.0.something on Suse 10.1.

BTW, I just tried the same searches at home using Firefox 2.0.0.10 on Suse 10.3 and the returned links seem to work. It seems weird that a browser would have the ability to cause that sort of trouble but that's what it looks like is happening. I guess I might have to upgrade at work before I can find an answer to that programming problem I ran into. :)

It's also possible you are browsing through a broken proxy at work. Do the links not work for anyone else?

--jeremy

I get the same thing:
(search for tcl/tk)

But it's fine if I search for "database" - the links work with no problems.

Odd, http://www.linuxquestions.org/questi...ghlight=tck/tl works as expected for me in both FF 2.0.0.9 and 2.0.0.11. What browser are you using?

--jeremy

Firefox 2.0.0.11 on XP. It seems to balk at the "/", I think. The search picks it up as %2F in the URL bar

I had someone with XP test this and I think I'm able to reproduce the issue reliably. We'll look into it ASAP. Thanks.

--jeremy

I suspect it's never come up because everyone else searches for "tcl tk" :)

This should be fixed. / was in our original test case, but we missed a scenario. Thanks again.

--jeremy

Works fine for me. Wish it was my thread so I could say it all works fine now :) Let's hope it fixes the problem for rnturn too :)