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

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: proton-0.10
• Fix Version/s: proton-0.10
• Component/s: proton-c
• Assignee: Unassigned
• Reporter: Ted Ross
• Created: 11/Aug/15 18:43
• Updated: 07/Jan/16 12:14
• Resolved: 12/Aug/15 19:36

Description

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.