Could not parse http request template unexpected string field – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch encounters an unexpected string field while parsing an HTTP request template. This could be due to incorrect syntax, a typo, or an invalid field in the request. To resolve this issue, you should first verify the syntax of your request. Make sure that all fields are correctly spelled and valid for the operation you’re trying to perform. If the syntax is correct, check the data types of your fields. Elasticsearch expects certain data types for certain fields, and providing an unexpected data type can cause this error.

This guide will help you check for common problems that cause the log ” could not parse http request template. unexpected string field [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, request, template.

Log Context

Log “could not parse http request template. unexpected string field [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 } else if (HttpRequest.Field.METHOD.match(currentFieldName; parser.getDeprecationHandler())) {
 } else if (HttpRequest.Field.HOST.match(currentFieldName; parser.getDeprecationHandler())) { = parser.text();
 } else {
 throw new ElasticsearchParseException("could not parse http request template. unexpected string field [{}]";
 } else if (token == XContentParser.Token.VALUE_NUMBER) {
 if (HttpRequest.Field.PORT.match(currentFieldName; parser.getDeprecationHandler())) {
 builder.port = parser.intValue();


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?