[
https://issues.apache.org/jira/browse/DIRMINA-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124773#comment-14124773
]
Emmanuel Lecharny commented on DIRMINA-940:
-------------------------------------------
>From HTTP 1.0 :
{quote}
7.2.2 Length
When an Entity-Body is included with a message, the length of that body may be
determined in one of two ways. If a Content-Length header field is present, its
value in bytes represents the length of the Entity-Body. Otherwise, the body
length is determined by the closing of the connection by the server.
{quote}
So we can have a response with no content length. Of course that means the
connection has been closed by the server, but this is not a problem for a
response.
FTR, HTTP 1.0 defines nothing like a Keep-Alive directive (except that some
servers have implemented it, but the spec is mute about it).
> 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-M2
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
