Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

StompEncoder should never produce more than one 'content-length' header [SPR-11984] #16600

Closed
spring-projects-issues opened this issue Jul 11, 2014 · 0 comments
Assignees
Labels
in: messaging type: bug
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jul 11, 2014

Rossen Stoyanchev opened SPR-11984 and commented

The StompEncoder writes a "content-length" header for STOMP frames that have a body. If however the message already contains such a header the result is two such headers in the serialized output.

In most cases an application sends messages through SimpMessagingTemplate or by returning from an @MessageMapping method. In both cases the content-length header is not set so this is unlikely to affect applications.


Affects: 4.0.6

Referenced from: commits b318880

@spring-projects-issues spring-projects-issues added type: bug in: messaging labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.1 RC1 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging type: bug
Projects
None yet
Development

No branches or pull requests

2 participants