Return-Path: Delivered-To: apmail-jakarta-httpclient-user-archive@www.apache.org Received: (qmail 42057 invoked from network); 18 Nov 2007 07:07:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Nov 2007 07:07:25 -0000 Received: (qmail 59027 invoked by uid 500); 18 Nov 2007 07:07:11 -0000 Delivered-To: apmail-jakarta-httpclient-user-archive@jakarta.apache.org Received: (qmail 59013 invoked by uid 500); 18 Nov 2007 07:07:11 -0000 Mailing-List: contact httpclient-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: "HttpClient User Discussion" Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-user@jakarta.apache.org Received: (qmail 59002 invoked by uid 99); 18 Nov 2007 07:07:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 17 Nov 2007 23:07:11 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [212.227.126.171] (HELO moutng.kundenserver.de) (212.227.126.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 18 Nov 2007 07:07:00 +0000 Received: from [85.180.46.146] (e180046146.adsl.alicedsl.de [85.180.46.146]) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis) id 0MKwpI-1IteF1131S-0008Ne; Sun, 18 Nov 2007 08:06:51 +0100 Message-ID: <473FE4CD.5030305@dubioso.net> Date: Sun, 18 Nov 2007 08:07:57 +0100 From: Roland Weber User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.9) Gecko/20071109 SeaMonkey/1.1.6 MIME-Version: 1.0 To: HttpClient User Discussion Subject: Re: Problem with MultiPartPostMethod when long string added in parameter References: <10ee68930711160245t46b37e1es666e5ad7764d72c2@mail.gmail.com> In-Reply-To: <10ee68930711160245t46b37e1es666e5ad7764d72c2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1/0A3aJZLnTWA63E2GUgc4OmkA40hE2OjLOoTU Mq+JLFFIJDUetQsthBUffeeufKhNeQ0nGNPzKBYiAqRo0aHOaC i7boQzdKom4SSh8ZTxreCs98NXIOmEp X-Virus-Checked: Checked by ClamAV on apache.org nitya vyas wrote: > > The problem i am facing is that i have a String parameter which will store > number of files being uploaded in comma separated string.. 1,2,3,... etc Why would you do that? If it's just all numbers from 1 to n, then send n instead and let the server interpret that. In general, you cannot assume that a server will be able to process parameters with arbitrary length, or that all browsers will be able to generate them. Limits are implementation specific. > The value which i get for the long string parameter 1,2,3,4,5.. upto 300 is > not got properly and there are garbage values in that... Can you be more specific about the garbage values? Something like line breaks? > wat can be done to get the value of the long string correctly by > parseRequest on server?? I suggest you use the wire log on the client side to get the exact value that is sent for the parameter. Compare something that works (...200) with one that fails (...300). Then we can check whether what we send is comopliant with the spec. As mentioned above, the best way to fix this problem is to avoid excessively long parameter values. hope this helps, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: httpclient-user-help@jakarta.apache.org