You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2008/08/03 07:35:44 UTC
[jira] Created: (ASYNCWEB-18) the response after the continue (100)
response may not be handled properly
the response after the continue (100) response may not be handled properly
--------------------------------------------------------------------------
Key: ASYNCWEB-18
URL: https://issues.apache.org/jira/browse/ASYNCWEB-18
Project: Asyncweb
Issue Type: Bug
Components: Client
Affects Versions: client-1.0.0
Reporter: Sangjin Lee
Assignee: Sangjin Lee
The state transition for the HTTP response decoding is not correct for some continue responses. Currently, once the continue response is completely read, the state transitions to STATUS_READ immediately, and begins looking for the status line in the next response. However, if the status line is not found in the current buffer, it aborts processing but leaves the state in STATUS_READ. This is incorrect as obviously the status line has not been read. As a result, a ProtocolDecoderException is subsequently thrown.
This happens if the current buffer does not contain the full status line for the next (actual) response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (ASYNCWEB-18) the response after the continue (100)
response may not be handled properly
Posted by "Sangjin Lee (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ASYNCWEB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangjin Lee closed ASYNCWEB-18.
-------------------------------
Resolution: Fixed
Fix Version/s: client-1.0.0
If we fail to read the full status line, the state should be reset to the start state. The fix has been checked in.
> the response after the continue (100) response may not be handled properly
> --------------------------------------------------------------------------
>
> Key: ASYNCWEB-18
> URL: https://issues.apache.org/jira/browse/ASYNCWEB-18
> Project: Asyncweb
> Issue Type: Bug
> Components: Client
> Affects Versions: client-1.0.0
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Fix For: client-1.0.0
>
>
> The state transition for the HTTP response decoding is not correct for some continue responses. Currently, once the continue response is completely read, the state transitions to STATUS_READ immediately, and begins looking for the status line in the next response. However, if the status line is not found in the current buffer, it aborts processing but leaves the state in STATUS_READ. This is incorrect as obviously the status line has not been read. As a result, a ProtocolDecoderException is subsequently thrown.
> This happens if the current buffer does not contain the full status line for the next (actual) response.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.