[ https://issues.apache.org/jira/browse/QPID-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451480#comment-15451480 ]
Keith Wall commented on QPID-7408: ---------------------------------- I realise that there is a second related defect. If {{org.apache.qpid.server.management.plugin.HttpManagementConfiguration#isCompressResponses}} is set true, currently the {{HttpManagementUtil#getOutputStream()}} will attempt to recompress the compressed message content again. > REST API streams compressed message content without a Content-Encoding header > ----------------------------------------------------------------------------- > > Key: QPID-7408 > URL: https://issues.apache.org/jira/browse/QPID-7408 > Project: Qpid > Issue Type: Bug > Components: Java Broker > Affects Versions: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1 > Reporter: Keith Wall > Assignee: Lorenz Quack > Priority: Minor > Fix For: qpid-java-6.1 > > > 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. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org