Google Search Appliance User Experience Guide - Manual (Page 8)

8
The client query parameter controls which front end is used in serving search results. The following
table provides details about client.
Parameter Possible Value Description
client omitted Required parameter. If this parameter does not have a valid value,
other parameters in the query string do not work as expected.
front end name A string that indicates a valid front end and the policies defined for it,
including:
● KeyMatches
● Related Queries
● Filters—Enabling Query Expansion & Results Biasing Policies.
Filtering content by metadata, language, document type or
domain.
● Remove URLs
● OneBox Modules
● Dynamic Navigation
Notice that the rendering of the front end is determined by the
proxystylesheet parameter.
Example
http://GSA_HOSTNAME/search?site=default_collection&client=default_frontend&ou
tput=xml_no_dtd&proxystylesheet=default_frontend&proxycustom=%3CHOME/%3E
Review: Which presentation method should you use?
Use the following table to choose the method that best suits your needs.
Method When to use it
XSLT stylesheet Use this option when you want to serve formatted results directly from the search
appliance. You can use the Page Layout Helper to make quick and easy changes
such as adding your own logo, changing the header and footer, as well as basic
results options. You can also edit the XSLT stylesheet directly; this enables you to
customize every aspect of the results pages. This is also useful if you want to return
your own XML schema, RSS, or JSON.
XML output If you exclude the proxystylesheet parameter in the request URL, the search
appliance returns raw XML. This is useful if you have a multi-tier architecture, and
want to handle the presentation yourself.