qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Wall (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-7711) [Java Broker] Set correct Content-Encoding in REST response (6.0.x)
Date Tue, 28 Mar 2017 11:25:41 GMT

    [ https://issues.apache.org/jira/browse/QPID-7711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944980#comment-15944980

Keith Wall commented on QPID-7711:

This defect was fixed already on trunk and 6.1.x.   These changes should be ported to 6.0.x

> [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
>             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

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message