[
https://issues.apache.org/jira/browse/AMQ-7327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16972593#comment-16972593
]
ASF subversion and git services commented on AMQ-7327:
------------------------------------------------------
Commit 1846df4863b26e4290359b2bb2d69d6a832dd30f in activemq's branch
refs/heads/master from Jean-Baptiste Onofré
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=1846df4 ]
Merge pull request #410 from jbonofre/AMQ-7327
[AMQ-7327] Use maxFrameSize to limit HTTP content length
> HTTP transport connector doesn't limit the message size using maxFrameSize
> --------------------------------------------------------------------------
>
> Key: AMQ-7327
> URL: https://issues.apache.org/jira/browse/AMQ-7327
> Project: ActiveMQ
> Issue Type: Bug
> Components: Transport
> Affects Versions: 5.15.10
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.0, 5.15.11
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The {{ws}} transport connector uses the {{maxFrameSize}} to set binary and
> text message size limit.
> However the {{http}} transport connector doesn't and the user needs a hack on
> {{jetty.xml}}.
> The {{http}} transport connector should directly use the {{maxFrameSize}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
