Ruby's STOMP client always sets the content-length header and does not provide a mechanism to override the behavior. In addition, the 1.0 STOMP specification states the content-length header is optional but recommended. I implemented the feature discussed in
AMQ-739 utilizing the 'amq-msg-type' header to select the message type. I've only implemented 'text' and 'byte' message types.