Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
HTTP GELF endpoint returns 415 when specifying a charset in the Content-Type header #3477
When posting to a HTTP GELF endpoint and specifying a charset in the Content-Type header (
We are using Arebis.Logging.GrayLog in our .NET code, which automatically generates the headers and posts to Graylog via HTTP GELF.
I expect Graylog to accept the message, as it did in 2.1.
Graylog responds with a HTTP 415 Unsupported Media Type.
Accept valid Content-Type headers.
Steps to Reproduce
To Repro on Graylog 2.2
Unable to Repro on Graylog 2.1.3
With this change to Graylog 2.2, we are unable to ingest log messages from our .NET Clients. We can modify the logging library locally, but this seems like a bug in Graylog's handling of HTTP requests rather than a bug in the client logging library.
We are also experiencing this problem in our application, which uses the Fetch API in the browser to send GELF messages to Graylog (using https://github.com/ccapndave/grayconsole). This is a bit of a showstopper for us as