beautypg.com

Users see 404 errors after clicking results, Unexpected authorization behavior, Primary search appliance – Google Search Appliance Configuring GSA Unification User Manual

Page 23

background image

Google Search Appliance: Configuring GSA Unification

23

Users See 404 Errors After Clicking Results

Different configuration problems cause 404 errors when users click search results.

Check the URL patterns in the Follow and Crawl Only URLs settings on the primary and secondary
search appliances. Ensure that all Follow and Crawl Only URLs on the secondary appliances also
appear on the primary search appliance.

If you are using a database crawl, a user might see a 404 error after clicking a search result. When this
happens, it means that the primary search appliance is not set up with the database configuration
information from the secondary search appliances. To correct the error, copy the database
configuration information from the secondary search appliances to the primary search appliance.

Results from Secondary Search Appliances are Not
Available on Primary Search Appliance

If you find that results from the secondary search appliances are not available on the primary search
appliance, check the names of the composite collections. If different collections designated as part of a
composite collection have the same name, the site parameter is expanded at query time in such a way
that the results are not available on the primary search appliance. If this is the case, you can obtain
results from the secondary search appliances on http://0:9999/search, but not through the configured
front ends.

If you find that results from the secondary search appliances are not available on the primary search
appliance, ensure that nodes are added as secondary nodes only on the primary search appliance. Do
not add secondary search appliances to other secondary search appliances.

In addition, ensure that composite collections are configured only on the primary search appliance.

Unexpected Authorization Behavior

If you configure delegated authorization incorrectly, you encounter unexpected authorization behavior.
If you are using delegated authorization, ensure that it is enabled on the primary and all secondary
search appliances in the unified environment.

If delegated authorization is enabled only on the primary search appliance and not on the
secondary search appliances, the secondary search appliances do not perform authorization. Only
the primary search appliance is performing authorization.

If delegated authorization is disabled on the primary search appliance but enabled on the
secondary search appliances, the secondary search appliances perform authorization, but the
primary search appliances ignores the authorization and performs its own.