You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Keith Wall (JIRA)" <ji...@apache.org> on 2016/08/30 13:39:20 UTC
[jira] [Created] (QPID-7408) REST API streams compressed message
content without a Content-Encoding header
Keith Wall created QPID-7408:
--------------------------------
Summary: 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: qpid-java-6.0, 0.32, 0.30, qpid-java-6.1
Reporter: Keith Wall
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-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org