Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1126525

Summary: [AMQP 1.0] Can't read content endoding property
Product: Red Hat Enterprise MRG Reporter: Gordon Sim <gsim>
Component: qpid-cppAssignee: Gordon Sim <gsim>
Status: CLOSED ERRATA QA Contact: Petr Matousek <pematous>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0CC: jross, pematous, zkraus
Target Milestone: 3.1Keywords: Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: qpid-cpp-0.30-2 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-14 13:48:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Gordon Sim 2014-08-04 15:55:36 UTC
Description of problem:

There is no way to get at the AMQP 1.0 content encoding field via qpid::messaging

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Send a message with content encoding in it (e.g. using qpid::messaging with 1.0 add a property x-amqp-content-encoding)
2. Receive the message and check for x-amqp-content-encoding property

Actual results:

No such property is reported as present

Expected results:

The property in the encoded message should be returned to the application

Additional info:

Comment 1 Gordon Sim 2014-08-04 17:32:42 UTC
Fixed upstream:

Comment 3 Petr Matousek 2014-12-12 10:52:45 UTC
AMQP 1.0 content encoding now accessible via x-amqp-content-encoding message field in qpid::messaging API.

Verified on rhel6.6 (x86_64 and i386)



Comment 5 errata-xmlrpc 2015-04-14 13:48:19 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.