Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mfncooper@gmail.com designates
 66.249.82.206 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references;
        b=DQRmxIUooZAQ8AKRe5FZywbYAAZoAs419l3UA4TLT6eX+IzTRO6fOZAQcArXsBGlq/K5fk/bDaK+p0MbGI5J5KClHZf7fqb+F3Mqo5HifilWbPLW40QedwbI4y4f6DeqTUS4SqP0lOR27CgqWwjbW79llf+Tkf3ED0FzWXWz+sM=
Message-ID: <16d6c6200511171409s20c2c95ajfb2a282ecded52c7@mail.gmail.com>
Date: Thu, 17 Nov 2005 14:09:18 -0800
From: Martin Cooper <martinc@apache.org>
Sender: mfncooper@gmail.com
To: Jakarta Commons Users List <commons-user@jakarta.apache.org>
Subject: Re: [FileUpload] Exception during request parsing
In-Reply-To: 
 <95AA550E36EB1C42BF9B0BFCF145CE190212432E@srv-web-sp1.dev.mm.atos.fr>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1587_15958087.1132265358604"
References: 
 <95AA550E36EB1C42BF9B0BFCF145CE190212432E@srv-web-sp1.dev.mm.atos.fr>

------=_Part_1587_15958087.1132265358604
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On 11/17/05, Belot Thomas <Thomas.Belot@atosorigin.com> wrote:
>
> Thank you for your answers Martin, here's my response :
>
> >Because that would limit it to JDK 1.4 or later.
> Ok, now I understand why.
>
> >The most common cause of this is that the request has already been
> consumed,
> >and is therefore no longer available for parsing by FileUpload.
>
> >Because it didn't open it. Whoever opened it should close it.
>
> No, FileUpload is the only one accessing request.getInputStream() in my
> code (by the way I didn't knew that one could use the InputStream before
> giving it to file upload without crashing fileUpload.parse).
> That's why I assumed file upload was supposed to close it.


What I mean is that, for Tomcat at least, getInputStream() does not open th=
e
input stream, it simply returns one that was already open. The container
opens it, so the container should be closing it. (And no, you can't do
anything with the input stream before FileUpload parses it.)

--
Martin Cooper


Best regards
>
> Thomas
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-user-help@jakarta.apache.org
>
>

------=_Part_1587_15958087.1132265358604--