Ok, so I am unsure if it is a bug but in my opinion it is not a desired behaviour:
Steps to reproduce:
- Create a request for query any would do
- In the header make sure value is ContentType: application/json; charset=utf-8
- Execute the query.
- The server complains the request sent is not application/json and ask for it.
In reality, the charset is utf-8 by default, however this should not result dgraph complaining the request is not
application/json as it. The server should be smart enough to handle that in my humble opinion.