activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (Resolved) (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Resolved] (AMQNET-345) NMS.Stomp doesn't properly encode or decode header values according to the Stomp v1.1 spec
Date Thu, 03 Nov 2011 23:49:32 GMT

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

Timothy Bish resolved AMQNET-345.
---------------------------------

    Resolution: Fixed
      Assignee: Timothy Bish  (was: Jim Gomes)

Fix applied in trunk and 1.5.x branch
                
> NMS.Stomp doesn't properly encode or decode header values according to the Stomp v1.1
spec
> ------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-345
>                 URL: https://issues.apache.org/jira/browse/AMQNET-345
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: Stomp
>    Affects Versions: 1.5.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 1.5.2, 1.6.0
>
>
> When connected to a Stomp v1.1 broker the client needs to dead with encoding and decoding
of header values according to the spec.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message