[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2

2018-02-12 Thread Justin Ross (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated QPID-8084:
--
Fix Version/s: qpid-python-1.38.0

> 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
> Fix For: qpid-python-1.38.0
>
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2

2018-02-02 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPID-8084:
---
Status: Reviewable  (was: In Progress)

> 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
(v7.6.3#76005)

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



[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2

2018-02-01 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPID-8084:
---
Summary: QMF management client sends binary application property keys under 
Python 2  (was: Python binding accepts binary keys for message application 
properties)

> 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
(v7.6.3#76005)

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



[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2, Qpid-cpp broker accepts it.

2018-01-22 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPID-8084:
---
Component/s: Python Client

> QMF management client sends binary application property keys under Python 2, 
> Qpid-cpp broker accepts it.
> 
>
> 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
>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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2, Qpid-cpp broker accepts it.

2018-01-22 Thread Justin Ross (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Justin Ross updated QPID-8084:
--
Labels: interop  (was: )

> QMF management client sends binary application property keys under Python 2, 
> Qpid-cpp broker accepts it.
> 
>
> 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
>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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2, Qpid-cpp broker accepts it.

2018-01-22 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPID-8084:
---
Description: 
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.

  was:
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.


> QMF management client sends binary application property keys under Python 2, 
> Qpid-cpp broker accepts it.
> 
>
> Key: QPID-8084
> URL: https://issues.apache.org/jira/browse/QPID-8084
> Project: Qpid
>  Issue Type: Bug
>Reporter: Kim van der Riet
>Priority: Major
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org



[jira] [Updated] (QPID-8084) QMF management client sends binary application property keys under Python 2, Qpid-cpp broker accepts it.

2018-01-22 Thread Kim van der Riet (JIRA)

 [ 
https://issues.apache.org/jira/browse/QPID-8084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim van der Riet updated QPID-8084:
---
Attachment: py2.pcapng

> QMF management client sends binary application property keys under Python 2, 
> Qpid-cpp broker accepts it.
> 
>
> Key: QPID-8084
> URL: https://issues.apache.org/jira/browse/QPID-8084
> Project: Qpid
>  Issue Type: Bug
>Reporter: Kim van der Riet
>Priority: Major
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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