Problem with Search function
#1
Guest
Posts: n/a
Problem with Search function
I got so excited! I tried doing a search and the results came back in two seconds! Wow, I thought, they really improved this. BUT, I wasn't able to open any of the<BR>resulting messages, I keep getting a window that says "Bad Request". I've tried reloading, and I've tried doing the search again from scratch.<BR>Anyone else having this problem?
#5
Guest
Posts: n/a
thanks all but I still can't open any of the messages from the search results<BR><BR>However, since Fodor's is now numbering them, I went back to the regular screen and scrolled down (for weeks!) until I got to one of the threads and opened one of them that way
Trending Topics
#9
Guest
Posts: n/a
I guess the "exact match" button no longer means anything. When I tried to find my own old post about Dolomite Hotels, I entered "Hotels in Dolomites" and carefully left the exact match button unchecked. The search function came up with "nothing matches". I went through the list and finally found it, "Hotels in the Dolomites". Seems that if I weren't asking for an exact match the search function should have found that!
#12
Guest
Posts: n/a
Are you all using Netscape? When I try to open an answer in Netscape, I get the "Bad Request" answer. I often get these strange quirks on Netscape. On Internet Explorer the search answers open just fine.<BR>But to add to the confusion get this:<BR>When I put in the hotel name "domus julia", Netscape gives me results that I can't open. On Internet Explorer it says there is "no match". It's a Catch 22!
#14
Guest
Posts: n/a
Looking at Gerry's message it looks like it's an issue with the way Netscape sends over spaces. A workaround is to do the search like you normally do, then right click on the URL. You will get a bad request but then click on the URL and replace the space with a %20, e.g.<BR><BR>searchtext=domus%20julia.<BR><BR>That works. I am sure Fodors will fix it. I have seen this happen at some sites.
#15
Guest
Posts: n/a
Just tried locating a past post using Netscape and got the dreaded "Bad request" message. Tried locating the same post using Explorer, and it came up with no problem. I'm not literate enough to know what this means, but am reporting it in case it helps someone else.


