Page 1 of 1

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 1:42 pm
by jgdoke
This may have something to do with this patch. we just implemented it in may and have had the issue since then.
http://thunderstone.master.com/texis/ma ... 467bf4322e
All search styles work correctly except XSL, I have created a default crawl with only default settings.
Scripts version 6.3.1
with query logging turned on the url is this:
http://searchext.ra.rockwell.com/texis/ ... rotection/
I understand it is a redirect. the issue is Where the appliance is coming up with: searchext.ra.rockwell.com?
We cannot find it anywhere in the appliance.
With any other search style the url is this:
http://search2.rockwellautomation.com/t ... rotection/

And search2.rockwellautomation.com is the correct url to the box.
Please tell us where this setting is or how the url is constructed with XSL so we can try to figure this out.

Thanks

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 1:55 pm
by mark
The hostname in the query log url should be the same as the one used by the user to access the search.

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 2:05 pm
by jgdoke
I understand that is how it SHOULD work. but something is wrong and the XML output is putting the odd front on the url's. "We" are not doing this. The appliance is doing it and we need to figure out how and where so we can fix it.

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 2:50 pm
by mark
Is this a meta search?

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 3:22 pm
by jgdoke
No a standard search

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 3:46 pm
by mark
See what you have the appliance's hostname set to in Maintenance->Webmin->Network Configuration->DNS Client

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 5:07 pm
by John
The hostname is derived from the Host: header for the XSL results, whereas it is a relative URL in HTML results. If you have a load-balancer, proxy or other front-end that is changing the Host: header that could cause the issue.

XSL ClickUrl is not properly formatted, it has the wrong server on the front

Posted: Thu Jul 31, 2008 5:44 pm
by jgdoke
You are exactly correct. the proxy was putting it on.
Thanks