Tuesday, 9 November 2010

Google Search Appliance - Not following the (re)directions

We were seeing a problem where we couldn't access the GSA on port 80 or 443, instead receiving: -

The page isn't redirecting properly

Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

    *   This problem can sometimes be caused by disabling or refusing to accept
          cookies.

It turned out to have been a misconfiguration; the GSA was effectively redirecting requests back to itself :-)

Under System Settings, the Default Search URL -> Redirect requests for '/' setting was set to '/'.

Initially, I replaced the '/' with the FQ URL of the default collection and default front-end: -

http://10.65.127.54/search?site=default_collection&client=default_frontend&output=xml_no_dtd&proxystylesheet=default_frontend&proxycustom=%3CHOME/%3E

which worked OK.

I then simply blanked out the value, and again it seems to work.

In both cases, it redirects to the default front-end / collection: -

http://10.65.127.54/search?site=default_collection&client=default_frontend&output=xml_no_dtd&proxystylesheet=default_frontend&proxycustom=%3CHOME/%3E

The thing that drew me to this was that the HTTPFox plugin threw up a (NS_ERROR_REDIRECT_LOOP) exception after a number of HTTP 302 redirections

No comments:

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...