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

Average Read Time

2 Mins

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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 a demo of the Check-Up:

Analyze your cluster