Return-Path: Delivered-To: apmail-mina-dev-archive@www.apache.org Received: (qmail 29713 invoked from network); 6 Dec 2007 05:17:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Dec 2007 05:17:04 -0000 Received: (qmail 93427 invoked by uid 500); 6 Dec 2007 05:16:52 -0000 Delivered-To: apmail-mina-dev-archive@mina.apache.org Received: (qmail 93393 invoked by uid 500); 6 Dec 2007 05:16:52 -0000 Mailing-List: contact dev-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mina.apache.org Delivered-To: mailing list dev@mina.apache.org Received: (qmail 93384 invoked by uid 99); 6 Dec 2007 05:16:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Dec 2007 21:16:52 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Dec 2007 05:16:40 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2EDD5714240 for ; Wed, 5 Dec 2007 21:16:43 -0800 (PST) Message-ID: <16964763.1196918203133.JavaMail.jira@brutus> Date: Wed, 5 Dec 2007 21:16:43 -0800 (PST) From: "Vishal (JIRA)" To: dev@mina.apache.org Subject: [jira] Updated: (DIRMINA-487) Fix HTTP response with no content-length header In-Reply-To: <1520323.1196866483500.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DIRMINA-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal updated DIRMINA-487: --------------------------- Description: HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this. (was: HTTP/1.1 responses (content part) which have the content-length header missing are accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protcol filter needs to be fixed for this.) > Fix HTTP response with no content-length header > ----------------------------------------------- > > Key: DIRMINA-487 > URL: https://issues.apache.org/jira/browse/DIRMINA-487 > Project: MINA > Issue Type: Bug > Components: Protocol - HTTP, Statemachine > Affects Versions: 2.0.0-M1 > Environment: All platforms > Reporter: Vishal > Fix For: 2.0.0-M1 > > > HTTP/1.1 responses (content part) which have the content-length header missing are not accepted properly. The HTTP spec hints at reading the content until the connection is closed if the response length or chunk size is not mentioned. The Http protocol filter needs to be fixed for this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.