StompSubProtocolHandler makes the same assumption about header accessor as SimpleBrokerMessageHandler used to [SPR-14791] #19357
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
status: backported
An issue that has been backported to maintenance branches
type: enhancement
A general enhancement
Milestone
Dave Syer opened SPR-14791 and commented
Just like in #18851,
StompSubProtocolHandler.getStompHeaderAccessor()
makes an assumption about the content of theMessage
it is processing. In particular, it assumes that there is aMessageHeaderAccessor
, but that isn't necessarily the case, for instance if the user has added aChannelInterceptor
that rebuilds the message and adds some headers by callingMessageBuilder.fromMessage(...).build()
.Affects: 4.2.8, 4.3.3
Issue Links:
Referenced from: commits f5cd538, aff5d21, 66722af
Backported to: 4.2.9
The text was updated successfully, but these errors were encountered: