You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2012/07/05 23:08:34 UTC

[jira] [Resolved] (AMQ-3913) Stomp Spec allows for stomp headers to have spaces in key or value we currently trim.

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

Timothy Bish resolved AMQ-3913.
-------------------------------

    Resolution: Fixed
      Assignee: Timothy Bish

Fixed in trunk, tests were scrubbed already to ensure we send the correct headers. 
                
> Stomp Spec allows for stomp headers to have spaces in key or value we currently trim.
> -------------------------------------------------------------------------------------
>
>                 Key: AMQ-3913
>                 URL: https://issues.apache.org/jira/browse/AMQ-3913
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: stomp
>    Affects Versions: 5.6.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>            Priority: Minor
>             Fix For: 5.7.0
>
>
> The spec specification allows for spaces to exists at either end of a message header key or value.  We currently trim the header keys in order to be forgiving of clients that don't adhere to the this and send odd keys with space padding, we should now stop this and align more closely to spec compliant behavior.  This means some clients could see some oddness if they don't also ensure that keys we are looking for like 'destination' etc are not correctly formated on send. 

--
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