---
title: Intermittent 419 errors on Coveo Hive search interfaces
slug: n74a0288
canonical_url: https://docs.coveo.com/en/n74a0288/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# Intermittent 419 errors on Coveo Hive search interfaces


[.version.c4sc.c4sc-issue-resolved.5-0-1153-1.August-15&-2022]
[Issue resolved](https://docs.coveo.com/en/m3gf4364#release-notes)



[.version.c4sc.c4sc-issue-resolved.5-0-1153-1.August-15&-2022]
[Issue resolved](https://docs.coveo.com/en/m3gf4364#release-notes)


## Symptoms

Search interface page users get "419 expired token" errors intermittently.

## Cause

You may be caching the `/coveo/rest` reverse proxy endpoint.
Since the [October 30, 2020 release](https://docs.coveo.com/en/3360#release-notes), Coveo Hive search interfaces perform front-end calls through the reverse proxy endpoint to generate search tokens.
Storing search token call responses in an HTTP cache eventually leads to the retrieval of a Coveo search token that has expired.

## Resolution

The issue was resolved in the Coveo for Sitecore [August 15, 2022 release (5.0.1153.1)](https://docs.coveo.com/en/n3ne0564/).
We recommend you upgrade to the latest version of Coveo for Sitecore.

### Workaround

Disable the `/coveo/rest` reverse proxy endpoint response caching mechanisms, whether using Cloudflare or another service.