Thunderstone Support Forums

When we deliver results to the user (using the concise look - not actually tried any others) we get the webinator URL prepended on the result URL, rendering it useless... or maybe it's supposed to be that way and we have something set up poorly. Either way, it's not working.

An Example HREF :-
HREF="/texis/Webinator/search/redir.html?query=deploy&pr=default&prox=page&rorder=500&rprox=500&rdfreq=500&rwfreq=500&rlead=500&sufs=2&order=r&cq=&u=http%3A//iwww.obfuscated.com.au/index/stay_informed/information_and_resources/fire_information.htm">Fire Information


I'm obviously missing a setting somewhere, but just can't seem to find it!

The "/texis/Webinator/search/redir.html" is put on the front of result URLs when you have Query Logging on. This allows Webiantor to track when users click on a result.

What do you get when someone clicks on a result url?

They get a 404.... which now I reflect upon it, might be because I can find no trace of redir.html! This is a brand new installation, so unless that is a placeholder for the ISAPI filter to catch, that would seem to be the issue.

In any event, I've turned logging off for now and that at least gets my users working again.

redir.html shouldn't exist on disk - the stuff between "/search/" and ".html" specifies which function is used in the "search" script.

What version of windows is this?

Are there any sitewide ISAPI filters, or any other settings, that could possibly be interfering with the request before it gets to Webinator?

I'm assuming if you open /texis/Webinator/search directly it works ok? What about /texis/Webinator/search/redir.html? It should say "Error: search could not be executed" rather than "404".

I figured redir was might be an alias.

Win2003 Server, and yes there are some other ISAPI filters loaded, but they explicitly exclude any /texis/* URLs, so I don't think that is the issue.

Search works fine, and a direct call to redir as above generates, of all things, a DNS error!?