Error retrieving message content in large messages about stompjs HOT 4 CLOSED

Hello Kum,

You were right: our middleware was sending the content lenght incorrectly.

Now it's fixed in our side and the only "input" for you is that version 4.0.8 had, somehow, an incorrect implementation.

Thanks again. I close this ticket.

from stompjs.

I think I have an idea why it is happening.

As per STOMP standards, the content-length is length in octets (https://stomp.github.io/stomp-specification-1.2.html#Header_content-length). The version 4.0.8 has incorrect implementation.

I noticed the content-length in your frame is character length.

To get over it, the broker should send length in octets or should not send the content-length header at all.

from stompjs.

Aha,

We will look into the broker's implementation and provide some feedback in this thread. We're testing the new beta4 version and were surprised on this issue since the 4.0.8 version was running just fine (at least for us).

Thanks for your quick response, again.

from stompjs.

In all previous versions frame parsing had multiple minor issues, which all together made it work for most regular use cases. However, there was no easy way to support binary content - which can have NULLs.

This was one of the main motivations for the new version.

from stompjs.