Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ElasticSearch 7.12.0 responds with "Content-Type header [] is not supported" #18

Open
obi-jon opened this issue Apr 23, 2021 · 0 comments

Comments

@obi-jon
Copy link

obi-jon commented Apr 23, 2021

There appears to be a requirement from elasticsearch 7.12.0 to have a content-type header.

The configuration used here is the docker image for elasticsearch and kibana 7.12.0 in a network, a separate container running DVWA and burp pro on the local host pointed at elasticsearch.

The post from elastic burp does not include a Content-Type header
eb_post

The response from elasticsearch gives the impression that the Content-Type header is necessary
elastic_response

A text file following the HTTP thread. The data is from a burp scan of DVWA (no sensitive date)
elasticBurp.txt

Docker command used to run DVWA
docker run --name=dvwa -d vulnerables/web-dvwa

Docker-Compose Yaml file for ElasticSearch and Kibana
docker-compose.yml.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant