Google Search Appliance Security - Manual (Page 38)

38
Web proxy
The options described above are the most common platforms used to implement the security side of the
interconnection with a content source. There are others, such as using a web proxy to manage the
authorization.
In this case, the authorization is centralized in a web proxy that requires all URLs to be rewritten to go
through it. So the search appliance sends HTTP head requests to validate security before serving results.
Key considerations
Using a web proxy is similar to using a SAML authorization provider, but with the following disadvantages:
●
Authorization requests are not batched.
●
URLs have to be rewritten to go through the web proxy for authorization. For example:
http://proxy.corp.com/proxy?returnPath=http//cont.corp.com/doc.html
●
Those URLs that were rewritten are stored in the index in this manner and may have to be
translated again to the original URL in the search front end.