The Broker for Java supports compressed messages. If I view a compressed message through the management console, the Broker sends the content to the client without a Content-Encoding header, so the client treats the bytes as if they were uncompressed. If the message's mime type is text/*, I see seeming garbage instead of the inlined text content. If the message's mime type is something else the browser handles the content as if it were uncompressed. This could confused applications associated with the Browser.
This could potentially hinder an operator.