qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim van der Riet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QPID-8084) QMF management client sends binary application property keys under Python 2
Date Fri, 02 Feb 2018 20:13:00 GMT

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

Kim van der Riet commented on QPID-8084:

See PROTON-1758 for the issue as it relates to the Python binding making a check of the message
application property keys.

> QMF management client sends binary application property keys under Python 2
> ---------------------------------------------------------------------------
>                 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

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

View raw message