Input expected content type but read from headers; using expected one – How to solve related issues

Opster Team

Jan-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Input expected content type but read from headers; using expected one ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

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 “[{}] [{}] input expected content type [{}] but read [{}] from headers; using expected one” classname is ExecutableHttpInput.java.
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

             //Attempt to auto detect content type; if not set in response
            contentType = responseContentType != null ? responseContentType : XContentHelper.xContentType(response.body());
        } else {
            contentType = input.getExpectedResponseXContentType().contentType();
            if (responseContentType != contentType) {
                logger.warn("[{}] [{}] input expected content type [{}] but read [{}] from headers; using expected one"; type(); ctx.id();
                        input.getExpectedResponseXContentType(); responseContentType);
            }
        }

        if (contentType != null) {




 

Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content