[QPID-7408] [Java Broker] REST API streams compressed message content without a Content-Encoding header

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
• Fix Version/s: qpid-java-6.1, qpid-java-6.0.7
• Component/s: Broker-J
• Assignee: Keith Wall
• Reporter: Keith Wall
• Created: 30/Aug/16 13:39
• Updated: 02/Oct/19 19:22
• Resolved: 20/Sep/16 12:50

Description

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.

Issue Links

• is related to: QPID-7382 Message dialogue tries to inline the text of a text message content regardless of the its length
• is related to: QPID-7711 [Java Broker] Set correct Content-Encoding in REST response (6.0.x)