Uploaded image for project: 'Qpid'
  1. Qpid
  2. QPID-7408

[Java Broker] REST API streams compressed message content without a Content-Encoding header

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.30, 0.32, qpid-java-6.0, qpid-java-6.1
    • Fix Version/s: qpid-java-6.1, qpid-java-6.0.7
    • Component/s: Broker-J
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                k-wall Keith Wall
                Reporter:
                k-wall Keith Wall
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: