Bad regex in ” + SETTING_CORS_ALLOW_ORIGIN.getKey() + “: ” + origin + ” – How to solve this Elasticsearch error

Opster Team

July-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them.

This guide will help you check for common problems that cause the log ” Bad regex in ” + SETTING_CORS_ALLOW_ORIGIN.getKey() + “: ” + origin + ” ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: Node.


Log Context

Log “Bad regex in [” + SETTING_CORS_ALLOW_ORIGIN.getKey() + “]: [” + origin + “]”classname  is CorsHandler.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

builder = CorsHandler.Config.Builder.forOrigins(RestUtils.corsSettingAsArray(origin));
 } else {
 builder = CorsHandler.Config.Builder.forPattern(p);
 }
 } catch (PatternSyntaxException e) {
 throw new SettingsException("Bad regex in [" + SETTING_CORS_ALLOW_ORIGIN.getKey() + "]: [" + origin + "]"; e);
 }
 }
 if (SETTING_CORS_ALLOW_CREDENTIALS.get(settings)) {
 builder.allowCredentials();
 }

 

Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content