Disable the reverse proxy

Out of the box, a Coveo for Sitecore response processing proxy pipeline runs the ResolveResultClickableUriProcessor processor and resolves your item clickable URIs in the context of the current site.

In a scaled Sitecore environment, you’ll need to account for the fact your clickable URIs are not automatically recomputed at query time (for example, by ensuring your items are indexed with content delivery (CD) site URIs).

Search query requests and responses are relayed by the proxy. Server thread handling, proxy pipeline operations (for example, deserialization and reserialization of search request payloads), and processor execution increase overhead.

Your search requests are sent directly from your search interface to the Coveo search endpoint, resulting in shorter query durations.

Coveo for Sitecore provides pipelines to alter search queries before they’re sent to Coveo, and to handle and modify the Coveo responses. You can run your custom processors in these pipelines, leveraging Sitecore context (see About the REST endpoint pipelines).

You’ll need to consider using query pipeline features to alter search requests in Coveo before they’re sent to the index. Though query pipeline features are powerful, only the trigger feature lets you alter the query response, but not the search results themselves.

Using the proxy produces two hits on your server for each search and usage analytics request, increasing the load on your server.

Your server is hit only once for each search and usage analytics request. On hosted platforms (for example, Azure), where usage costs may depend on the number of hits to your backend, bypassing the proxy can translate into cost reductions.