You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/04/06 09:54:41 UTC
[jira] [Commented] (QPID-7408) REST API streams compressed message
content without a Content-Encoding header
[ https://issues.apache.org/jira/browse/QPID-7408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958679#comment-15958679 ]
ASF subversion and git services commented on QPID-7408:
-------------------------------------------------------
Commit 1790370 from orudyy@apache.org in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1790370 ]
QPID-7408,QPID-7711: Fix various issues with message content REST API
* Set correct Content-Encoding in REST responses for message content
* Avoid double compression when content is compressed and gzip compression is supported by the client
* Decompress compressed message content if compression is unsupported on client
The following commits have been merged with a lot of manual conflict resolutions (leaving only 6.0.x relative changes)
svn merge -c 1758395 ^/qpid/java/trunk
svn merge -c 1759379 ^/qpid/java/trunk
svn merge -c 1759829 ^/qpid/java/trunk
svn merge -c 1761399 ^/qpid/java/trunk
svn merge -c 1761561 ^/qpid/java/trunk
svn merge -c 1761567 ^/qpid/java/trunk
> 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: Keith Wall
> Priority: Minor
> Fix For: qpid-java-6.1
>
> Attachments: 0001-QPID-7408-Extend-gunzip-output-stream-from-InflaterO.patch, new-compression-tests.diff
>
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org