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

Robbie Gemmell updated PROTON-2034:
-----------------------------------
    Description: 
If a selector is provided via a non-unicode string, an illegal binary value is 
sent on the wire. The selector filter type is explicitly defined as being a 
string typed value. Some AMQP servers (e.g. Artemis, ActiveMQ) reject or 
mishandle the illegal value, rightfully expecting to be sent a string.

In Python 2.x, this is an easy mistake to make, as strings are non-unicode by 
default. The solution for the client to convert Python binary types to unicode 
before sending on the wire to the server.

  was:
If a selector is used with a non-unicode string, the Java AMQP servers 
(Artemis, ActiveMQ) reject it with an "Invalid parameter" error. It appears 
that these servers are expecting only uniocde strings for the selector, and 
will close the connection if any other type is received.

In Python 2.x, this is an easy mistake to make, as strings are non-unicode by 
default. The solution for the client to convert Python binary types to unicode 
before sending on the wire to the server.


> [python] Selector string sent as illegal binary value if non-unicode string 
> is used
> -----------------------------------------------------------------------------------
>
>                 Key: PROTON-2034
>                 URL: https://issues.apache.org/jira/browse/PROTON-2034
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: python-binding
>            Reporter: Kim van der Riet
>            Assignee: Kim van der Riet
>            Priority: Major
>
> If a selector is provided via a non-unicode string, an illegal binary value 
> is sent on the wire. The selector filter type is explicitly defined as being 
> a string typed value. Some AMQP servers (e.g. Artemis, ActiveMQ) reject or 
> mishandle the illegal value, rightfully expecting to be sent a string.
> In Python 2.x, this is an easy mistake to make, as strings are non-unicode by 
> default. The solution for the client to convert Python binary types to 
> unicode before sending on the wire to the server.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to