[
https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14682306#comment-14682306
]
ASF subversion and git services commented on PROTON-978:
--------------------------------------------------------
Commit 3103ea7435bb5fce5b58176ebd362169351c16a8 in qpid-proton's branch
refs/heads/0.10.x from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3103ea7 ]
PROTON-978: Fix server "pipelined" SASL frame read processing
- Previously we were erroneously trying to process the AMQP header
as a SASL frame.
> Framing errors after SASL exchange when max-frame-size is configured
> --------------------------------------------------------------------
>
> Key: PROTON-978
> URL: https://issues.apache.org/jira/browse/PROTON-978
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.10
> Reporter: Ted Ross
> Priority: Blocker
> Fix For: 0.10
>
> Attachments: commit-0d2ef9f, commit-34b4c6d
>
>
> Detected in Proton 0.10-RC2
> If the server side of a transport has a non-zero max-frame-size (e.g. 65536),
> framing errors will occur between the SASL and AMQP sections of the
> connection protocol because pn_read_frame will read the AMQP header as though
> it were a frame.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
