You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[receiver/otlpreceiver] errorHandler returns 500 when Content-Type is unsupported or malformed #15995
errorHandler in receiver/otlpreceiver/otlphttp.go encodes the error Status using the
request's Content-Type. When that type is neither protobuf nor JSON — unsupported (text/plain) or malformed (application/) — it drops the original status code and writes 500 {"code": 13, "message": "failed to marshal error message"}. Client errors such as a 401 from an auth extension are reported as server faults, so clients retry requests that can never succeed.
Steps to reproduce
Collector with the OTLP receiver and an authenticator on the HTTP endpoint:
500 Internal Server Error with {"code": 13, "message": "failed to marshal error message"}.
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Activity
boqu commentedon Sep 21, 2026
The PR to fix the issue.
[receiver/otlphttp] Preserve status code in error handler for unsuppo…