You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@mina.apache.org by "Victor N (Commented) (JIRA)" <ji...@apache.org> on 2011/12/07 22:20:40 UTC

[jira] [Commented] (ASYNCWEB-39) Parsing of fragmented request/response data is broken with MINA-2.0.0 or later

    [ https://issues.apache.org/jira/browse/ASYNCWEB-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164707#comment-13164707 ] 

Victor N commented on ASYNCWEB-39:
----------------------------------

Victor, thank you for the patch! It works, I tested both with & without connection pooling. "chunked" requests also work.

P.S. mina 2.0.2, asyncweb 2.x (taken from trunk some months ago)
                
> Parsing of fragmented request/response data is broken with MINA-2.0.0 or later
> ------------------------------------------------------------------------------
>
>                 Key: ASYNCWEB-39
>                 URL: https://issues.apache.org/jira/browse/ASYNCWEB-39
>             Project: Asyncweb
>          Issue Type: Bug
>          Components: Common
>            Reporter: Victor Antonovich
>         Attachments: HttpCodecFactory_MINA-2.0.0_fix.patch
>
>
> MINA-2.0.0 and later versions have DIRMINA-749 fix ( https://issues.apache.org/jira/browse/DIRMINA-749 ), which broke AsyncWeb request/response parsing in case of fragmented network data. HttpCodecFactory class doesn't care about session decoders tracking, so each next network data fragment in session is parsed with new instance of decoder.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira