[
https://issues.apache.org/jira/browse/AMQ-5777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550261#comment-14550261
]
Christopher L. Shannon commented on AMQ-5777:
---------------------------------------------
I took out the recalculation of maxCommandLength and maxHeaderLength and
amended my commit and pushed it up. After thinking about it last night, it's
not necessary and just adds extra overhead. For example, if someone set a
maxFrameSize at 1024 bytes but had headers larger than that, it would still
fail when it reached the content parsing section because the frame was too
large. My test cases that I added show this as well and specifically test this
condition. Let me know what you think of the updated commit.
> Implement and test maxFrameSize for STOMP
> -----------------------------------------
>
> Key: AMQ-5777
> URL: https://issues.apache.org/jira/browse/AMQ-5777
> Project: ActiveMQ
> Issue Type: Sub-task
> Components: Broker
> Affects Versions: 5.11.1
> Reporter: Christopher L. Shannon
> Assignee: Timothy Bish
>
> Implement and test {{maxFameSize}} for STOMP to help prevent DOS attacks.
> Testing should include TCP, SSL, NIO and NIO+SSL, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
