Misleading Error Message when Wildcards are disabled

[kmerz]

Expected Behavior

When leading wildcards are disabled the user would like to see an error telling him that on this graylog server leading wildcards are not allowed.

Current Behavior

When the user is using leading wildcards on a server where leading wildcards are not allowed he gets an error message that elastic search cannot parse his query:

Possible Solution

Parse the error from elasic search and display the user a clearer error message indicating that leading wildcards are not supported on this graylog server.

Steps to Reproduce (for bugs)

1. disable leading wildcards on your server with config option: allow_leading_wildcard_searches = true
2. run a query with leading wildcard

Your Environment

• Graylog Version: 4.0 pre beta

[kmerz]

Assigned to backend, because I think we need to capture the exception, parse it and make sure it is explained better. Please let me know if I am mistaken.

[luk-kaminski]

@kmerz -> Cannot see this problem any more on current version. I suggest closing the issue.