[jira] [Updated] (PROTON-978) Framing errors after SASL exchange when max-frame-size is configured

["Ted Ross (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/PROTON-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Ross updated PROTON-978:
----------------------------
    Attachment: commit-0d2ef9f

Test update to detect the issue.

> 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)