lmenezes/cerebro

rest client is missing headers

Open

#396 opened on Sep 5, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (5,411 stars) (721 forks)batch import
bughelp wanted

Description

If I try to make the request GET /_cluster/health through the REST interface, I get:

{
  "error": "Content-Type header is missing",
  "status": 406
}

I'm running AWS elasticsearch 6.7, and using a reverse proxy to get the signed request that AWS needs. If I curl to the proxy I get the expected response so I'm assuming the issue is in cerebro's rest client, and not the proxy (the curl command was copied from cerebro's rest interface).

Odly enough, the proxy is actually receiving this very same requests from cerebro's normal operation and it works well (for example /_cluster/health).

This is the proxy: https://github.com/mozilla-services/aws-signing-proxy

Contributor guide

Tech stack
javascriptnodejs
Domain
backendapi
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic understanding of HTTP headersFamiliarity with JavaScript/Node.js
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Look into cerebro's REST client implementation, likely in the src/clients or similar directory. The issue is that requests made through the REST interface are missing the Content Type header, while normal operations work. Investigate how HTTP requests are constructed and ensure that the Content Type header is set appropriately for REST API calls.