[
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16349326#comment-16349326
]
Kim van der Riet commented on QPID-8084:
----------------------------------------
The QMF client code should be updated to use the pattern
{noformat}
prop[u'string_key'] = u'string_value'
{noformat}
where keys and values are intended to be strings to solve this issue locally.
However, to check for this problem universally, a check will be needed in the
various Proton bindings for this condition.
> Python binding accepts binary keys for message application properties
> ---------------------------------------------------------------------
>
> Key: QPID-8084
> URL: https://issues.apache.org/jira/browse/QPID-8084
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
> Priority: Major
> Labels: interop
> Attachments: py2.pcapng
>
>
> The AMQP 1.0 spec states that message application property keys MUST be
> strings.
> Under Python 2.x, the QMF client communicates with the broker using binary
> strings as keys in the application properties to pass QMF commands.
> Two issues arise:
> # The Python client should not accept binary keys in application properties
> # The broker appears to accept this without warning or error. This could be
> considered undefined behavior, however.
> The reproducer can be found in QPID-8075. The attached Wireshark file shows
> the transfer in frame 18.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
