Prometheus JMX exporter incorrectly returns both Content-Length and Transfer-Encoding response headers for gzip compressed response in JBoss EAP 7 image

Solution Unverified - Updated -

Issue

Prometheus JMX exporter incorrectly returns both Content-Length and Transfer-Encoding response headers for gzip compressed response in JBoss EAP 7 image.

However, RFC 7230 - Section 3.3.2. Content-Length (and also the latest RFC 9112 - Section 6.2. Content-Length) expressly forbids returning both Content-Length and Transfer-Encoding response headers in a response:

A sender MUST NOT send a Content-Length header field in any message that contains a Transfer-Encoding header field.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP) 7.x
  • OpenShift Container Image
  • Prometheus JMX Exporter enabled by the environment variable AB_PROMETHEUS_ENABLE

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content