Changing search result URLs with reverse proxy

Hi,

we are currently in the process of rolling out our Sitefinity CMS. As we don't want our IIS to be directly connected to the internet, we are using a reverse proxy, which proxies the requests of the client to the IIS and returns the results back to the browser. 

So far this is working fine, except of one thing. The search results (as our proxy is calling an internal URL to reach Sitefinity) is providing URLs with the internal servername of the Sitefinity server instead of the public URL that has been requests. This somehow makes sense, as Sitefinity simply uses the hostname it has been called with, but for us that does not work, as the customer will not be able to reach the internal URLs.

e. g result: http://<internalurl>/corporate/article/2011/03/29/test

Is there a way, that we can force the search results to always provide a static FQDN to the client, so that the results results are valid for them?


Thanks
Winni

Hi Winfried,

It is possible i. The easiest option is modifying the search results control and changing the result item url. Please check this post

www.sitefinity.com/.../separating_search_results_in_multilingual_websites.aspx

Greetings,
Ivan Dimitrov
the Telerik team

Dear Ivan / Sitefinity Crew,

We have a problem that is perhaps related to this issue.

In the live version of our site, say www.ourlivesite.com, we are getting search results from our demosite, say www.ourdemosite.com, which is closed off from external entries.

When we type "demo" in the search box from sitefinity, two news items that were on the demo site are being shown, with links to the urls of the closed off demo site.

How could we prevent this? Are search indexes from the demo site being stored in the database?

Thanks in advance for your help.

Ruben Meintema

Hello Ruben,

The search results are stored in App_Data/Seach folder. There is no record in the database. You use the same search for both the websites or you have common data that is indexed. You can check from where the request comes from using the host name and prevent showing data from one website in another.

All the best,
Ivan Dimitrov
the Telerik team

Hi Ivan,

Thanks for your reply.

We have just made a new search index, so that also does the trick.

But next time we will know where to look for it!

Thanks a lot,

Ruben