List of domain-level collection redirections.
Search services are tied to a collection which is expected to be passed as a URL parameter (e.g.
...&collection=my-collection...). However, clients can also connect to the root page of a Funnelback server (e.g. http://search.company.com/ ) without specifying a collection. While the default behavior is to redirect such requests to a list of all the collections present on the server, a collection redirection can also be configured based on the domain name used to access the Funnelback server.
This is best used in a multi-tenant system where the Funnelback server can be accessed via different domain names. The domain name is then used to identify a collection and the client is redirected to the search page for it, with possible optional parameters (Setting a
form, or any other URL parameter).
- Each domain name should be present only once. If a domain name is present multiple times, the behaviour is undefined.
- Only relative URLs are permitted on the right-hand side. Redirecting to absolute URLs is not permitted for security reasons, to prevent malicious exploitation of the service to redirect users to illegitimate websites.
A text file, where each line contains:
- A domain name (e.g.
- An equal (
- The URL, relative to the Funnelback server, to which clients should be redirected.
search.company.com=/s/search?collection=company-web&profile=web mobile.search.company.com=/s/search?collection=company-web&form=mobile api.search.company.com=/s/search.json?collection=company-api