-
Known Issues
- Sitecore Indexes Not Loading
- Unable to Create the Search Context Error
- Inactivity Timeout During Rebuild
- Problem Loading the Ninject Assembly
- Internal Server Error When Querying the REST Service
- Editing the Properties of a Coveo Search MVC Component Freezes the Page Editor in IE11
- Error or Document Not Found Page After Rebuilding the Indexes
- Problem Registering Search Page Events in Sitecore Analytics Database
- High Memory Usage While Rebuilding Indexes
- Root Element of a Crawler for a Coveo Index is Invalid
- HTML Version of Indexed Items Are Showing an Error Page
- NullReferenceException on Tracking.Current When Executing a Request for a Quick View
- Getting log4net Errors When Attempting to Browse Sitecore Pages
- Inserting an Example Search Page Results in No Renderings
- An Index Should Be Configured for Database Web Error Is Preventing the REST Service From Loading
- Cannot Insert the Value Null Into Column ID, Table Instance_hostname_core.dbo.properties. Column Does Not Allow Nulls.
- ERROR Error in FileWatcher Internal Buffer Overflow While Installing Coveo for Sitecore
- Exception While Handling Sitecore ContentSearch IndexingFinishedEvent, Index Was Not Found
- Failed to Reactivate the Organization Message in Command Center
- Handler Coveosearchendpoint Has a Bad Module Managedpipelinehandler in Its Module List
- Items in Different Languages Are Not Automatically Indexed or Updated When Language Fallback Is Enabled
- Missing Valid xDB License
- Opening the Experience Explorer Sets the Static Context to 'Master'
- Prebinding Isn't Applied to Elements Within a Searchbox Container
- Publishing Multi-Language Sitecore Items Leads to a Large Amount of Files Being Indexed
- Sitecore 8.2 With WFFM Refuses to Start After Installing Coveo for Sitecore
- Sitecore.ContentSearch.SitecoreItemCrawler.IsAncestorOf(Item item) error
- Solr - Error When Initializing Coveo When Side-by-Side With Solr Is Enabled
- The RouteData Must Contain an Item Named 'Controller' Error With SXA
- Sitecore SXA Throws Errors When Upgrading From Coveo for Sitecore 4.1 to Coveo for Sitecore 5
- Unexpected Token When Editing Page With SXA Components in Experience Editor
- Select the Associated Content Dialog Not Popping Up in SXA 1.8
- Could Not Find Property skipFirstTimeSetupCheck Error
- Send Analytics to Sitecore Component Not Working in Sitecore 9
- Two Instances of the Same Search Page Component Have Been Added on a Page But Only One is Initialized
- Dynamic Placeholders Not Displaying Allowed Renderings in SXA
- Failed to Configure the Organization Error When Trying to Switch Organization
- SXA Coveo Facet Value Suggestions Rendering Item Overwriting Hive Item at Installation
- Issues When the Core Database Is Disabled on Content Delivery Servers
- Content Database 'master' Not Found on a Content Delivery Server
- Sitecore 9 Content Delivery Instance Crashes at Index Initialization
- Coveo Analytics Events Are Not Logged in Sitecore 9.1 Analytics
- Compilation Error in Diagnostic Page in Sitecore 7.5 and 8.0
- Ajax Error 500 When Using Special Characters in a Query
- Dynamic Facet Range Not Showing When Returning From a No Result Query
- Master Index Old Item Versions Not Getting Deleted in Sitecore 9.1+
- Unhandled Exception After Installing Coveo for Sitecore on Sitecore 8.0 or 8.1 Instance
- The coveoProcessParsedRestResponse Pipeline Is Not Being Executed
- Unhandled Exception in Content Editor Prior to Coveo for Sitecore Activation
- Could Not Find Configuration Node Error on CD
- Components Aren’t Rendering Or Analytics HTTP Requests Are Failing Intermittently
- Ad-Blocker Filter Lists Blocking Coveo for Sitecore Calls
Ajax Error 500 When Using Special Characters in a Query
Symptoms
When performing a query using special characters in a Coveo-powered search page, your browser console displays an error like the following:
Uncaught (in promise) e {message: "Request Error", status: 500, type: "Ajax Error (status: 500)", name: "Ajax Error (status: 500)"}Notably, using <, >, or # in a search query renders the search page ineffective, even after clearing the search box.
Cause
ASP.NET validates any incoming request by looking for potentially dangerous characters, such as <, >, and #.
The query is then stored in the browser local storage __coveo.analytics.history key.
Every subsequent query will use this value as actionsHistory in its call headers.
This is why subsequent queries can continue to trigger the error, even if the user cleans the search box.
Resolution
For Sitecore 7 and 8 instances, the issue has been resolved in the October 2019 release of Coveo for Sitecore 5.
Workaround
Regardless of the Sitecore version you have, you can disable the special character validation on requests executed under /coveo/rest.
-
Open the
web.configfile in a text editor.Sitecore 7 and 8 Open the
<SITECORE_INSTANCE_ROOT>\Website\web.configfile in a text editor.Sitecore 9 and 10 Open the
<SITECORE_INSTANCE_ROOT>\web.configfile in a text editor. -
Locate the
<system.web>element.<system.web> <!-- If requestValidationMode attribute of httRuntime node is set to 2.0, Sitecore requires this setting to be set to "false" for Sitecore client to work and it shouldn't be changed. You can however set ValidateRequest attribute in the @Page directive to "true" for your layout .aspx files. --> -
Just ahead of the
<system.web>element, add the<location path="coveo/rest">element shown below.<location path="coveo/rest"> <system.web> <httpRuntime requestValidationMode="2.0" requestPathInvalidCharacters="" /> </system.web> </location> <system.web> <!-- If requestValidationMode attribute of httRuntime node is set to 2.0, Sitecore requires this setting to be set to "false" for Sitecore client to work and it shouldn't be changed. You can however set ValidateRequest attribute in the @Page directive to "true" for your layout .aspx files. --> -
Save your changes.