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 2017/04/06 16:56:41 UTC
[jira] [Resolved] (QPID-7711) [Java Broker] Set correct
Content-Encoding in REST response (6.0.x)
[ https://issues.apache.org/jira/browse/QPID-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Keith Wall resolved QPID-7711.
------------------------------
Resolution: Fixed
Changes look reasonable to me. Tested manually with content above/below the truncation threshold, with messages that were both compressed and uncompressed and with HTTP plugin compression on and off.
> [Java Broker] Set correct Content-Encoding in REST response (6.0.x)
> -------------------------------------------------------------------
>
> Key: QPID-7711
> URL: https://issues.apache.org/jira/browse/QPID-7711
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: qpid-java-6.0.6
> Reporter: Lorenz Quack
> Assignee: Alex Rudyy
> Fix For: qpid-java-6.0.7
>
>
> Currently the message preview in the web management console is broken but the culprit seems to be the broker.
> When trying to preview a TextMessage the broker replies with a gzip compressed response but without setting the Content-Encoding to gzip. this results in a garbled message preview on the client side.
> As a workaround one can disable compression for the httpManagement plugin.
--
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