You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2014/07/02 14:27:25 UTC
[jira] [Resolved] (PROTON-543) Frame Parser error if input stream
is read before SASL is initialized in the transport
[ https://issues.apache.org/jira/browse/PROTON-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell resolved PROTON-543.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.8
> Frame Parser error if input stream is read before SASL is initialized in the transport
> --------------------------------------------------------------------------------------
>
> Key: PROTON-543
> URL: https://issues.apache.org/jira/browse/PROTON-543
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: 0.5, 0.6
> Reporter: Rajith Attapattu
> Assignee: Robbie Gemmell
> Fix For: 0.8
>
>
> If the input stream is read and passed into the transport, before the sasl() method of TransportImpl.java is called then the _inputProcessor defaults to FrameParser instead of being wrapped by the SASL frame parser.
> This causes a Frame Parsing error as it expects '0' as per the regular header but instead finds '3' which is the correct format if the process is the SASL frame parser.
> As per the discussion on @proton we decide to throw an exception if sasl is set after the input stream has been processed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)