[jira] [Commented] (PROTON-109) Proton should handle inbound max-frame size violations.
[ https://issues.apache.org/jira/browse/PROTON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13689425#comment-13689425 ] Ken Giusti commented on PROTON-109: --- Review board for proton-c patch: https://reviews.apache.org/r/12011/ Proton should handle inbound max-frame size violations. --- Key: PROTON-109 URL: https://issues.apache.org/jira/browse/PROTON-109 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 0.5 According to the spec, if the local proton-c client has configured a maximum frame size, and the remote attempts to send a frame that violates that size: A peer that receives an oversized frame MUST close the Connection with the framing-error error-code. Need to verify this behavior is handled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-109) Proton should handle inbound max-frame size violations.
[ https://issues.apache.org/jira/browse/PROTON-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13575846#comment-13575846 ] Rob Godfrey commented on PROTON-109: proton-j will also need this change implemented Proton should handle inbound max-frame size violations. --- Key: PROTON-109 URL: https://issues.apache.org/jira/browse/PROTON-109 Project: Qpid Proton Issue Type: Bug Components: proton-c, proton-j Reporter: Ken Giusti According to the spec, if the local proton-c client has configured a maximum frame size, and the remote attempts to send a frame that violates that size: A peer that receives an oversized frame MUST close the Connection with the framing-error error-code. Need to verify this behavior is handled. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
