mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julien Vermillard (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRMINA-940) HTTP Client decoder does not support responses without Content-Length header
Date Thu, 21 Mar 2013 20:27:15 GMT

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

Julien Vermillard commented on DIRMINA-940:
-------------------------------------------

if you have no content-length, nor chunked encoding, the end of content should be the close
of the TCP connection.
Of course this is not compatible with HTTP1.1/1.0 connection "keep-alive" features.

I think I seen that somewhere in the RFC ;)
                
> HTTP Client decoder does not support responses without Content-Length header
> ----------------------------------------------------------------------------
>
>                 Key: DIRMINA-940
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-940
>             Project: MINA
>          Issue Type: Bug
>          Components: Protocol - HTTP
>    Affects Versions: 2.0.7, 3.0.0-trunk
>            Reporter: Jeff MAURY
>            Priority: Minor
>              Labels: http, http-headers
>             Fix For: 2.0.8, 3.0.0-trunk
>
>
> When an HTTP response is decoded has not Content-Length header, it is rejected by the
decoder as it should be accepted according to the spec

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message