lmenezes/cerebro

rest client is missing headers

Open

#396 创建于 2019年9月5日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)JavaScript (5,411 star) (721 fork)batch import
bughelp wanted

描述

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

贡献者指南

技术栈
javascriptnodejs
领域
backendapi
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic understanding of HTTP headersFamiliarity with JavaScript/Node.js
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
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.