Could you get me the full session TCP dump. I remember doing a recent change so the the encoding only occurred in 1.1 but not 1.0. I may have messed something up.
Regards, Hiram FuseSource Web: http://fusesource.com/ Connect at CamelOne May 24-26 The Open Source Integration Conference On Fri, May 13, 2011 at 9:46 AM, Lionel Cons <[email protected]> wrote: > Hiram, > > I've noticed that the latest snapshot that I got does not encode > colons in headers (using STOMP 1.1). Here is a tcpdump: > > 0x0030: 7ab8 c81a 4d45 5353 4147 450a 7375 6273 z...MESSAGE.subs > 0x0040: 6372 6970 7469 6f6e 3a39 6239 6231 3238 cription:9b9b128 > 0x0050: 2d34 6463 6433 3461 392d 3466 6531 2d65 -4dcd34a9-4fe1-e > 0x0060: 6266 2d31 0a4a 4d53 5855 7365 7249 443a bf-1.JMSXUserID: > 0x0070: 6775 6573 740a 6d65 7373 6167 652d 6964 guest.message-id > 0x0080: 3a6d 7367 3a31 0a64 6573 7469 6e61 7469 :msg:1.destinati > 0x0090: 6f6e 3a2f 7175 6575 652f 7465 7374 0a74 on:/queue/test.t > > We see msg:1 instead of msg\c1. > > Cheers, > > Lionel >
