From httpclient-userslynnalexis@example.com Thu Oct 01 18:05:43 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 91430 invoked from network); 1 Oct 2009 18:05:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Oct 2009 18:05:43 -0000 Received: (qmail 42322 invoked by uid 500); 1 Oct 2009 18:05:42 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 42241 invoked by uid 500); 1 Oct 2009 18:05:41 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 42231 invoked by uid 99); 1 Oct 2009 18:05:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 18:05:41 +0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=SPF_HELO_PASS,SPF_PASS,URI_NOVOWEL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Oct 2009 18:05:28 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <lynnalexis@example.com>) id 1MtQ1b-0004Yz-QC for lynnalexis@example.com; Thu, 01 Oct 2009 11:05:07 -0700 Message-ID: <lynnalexis@example.com> Date: Thu, 1 Oct 2009 11:05:07 -0700 (PDT) From: d_clark <lynnalexis@example.com> To: lynnalexis@example.com Subject: HttpClient MultiPart file upload getting rejected MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: lynnalexis@example.com X-Virus-Checked: Checked by ClamAV on apache.org Hi, Hope this is the right forum for the question.=20 I=E2=80=99m able to successfully upload a file via a website. Now I want to= automate this process by using a HttpClient to send a MultiPart post request. The problem is that the requests kept getting rejected by the server due to "corrupt form data=E2=80=9D and that=E2=80=99s all the info I can get from = the server. That leaves me to compare the requests sent from the web browser (good) and from my Eclipse (bad). I see some differences but can=E2=80=99t tell what m= ight be causing the issue. Hopefully the experts in this forum can offer some help. Thanks. Here=E2=80=99s the request sent from Eclipse (rejected): Header part: POST /servlet/MultiHandlerServlet?handler=3Duploadfile&ftype=3DSingleTest&sessio= n=3D5FD7C716A553EDC777A344AE92CE3123 HTTP/1.1 User-Agent: Jakarta Commons-HttpClient/3.1 Authorization: Basic MDAwMTExNDQ0Njp0byQ4bWVybg=3D=3D Host: www.xxxxxxx.com Cookie: $Version=3D0; JSESSIONID=3DD23D72FFB75E7EC13121441A171C5180; $Path= =3D/ Content-Length: 469 Content-Type: multipart/form-data; boundary=3DPoNK69pnchJKwVLDEQ-phInJ_mC8R6e95M7OP Body part: --PoNK69pnchJKwVLDEQ-phInJ_mC8R6e95M7OP Content-Disposition: form-data; name=3D"BulkSingleFlag" Content-Type: text/plain; charset=3DUS-ASCII Content-Transfer-Encoding: 8bit Single --PoNK69pnchJKwVLDEQ-phInJ_mC8R6e95M7OP Content-Disposition: form-data; name=3D"file"; filename=3D"testfile.xfd" Content-Type: application/vnd.adobe.xfd+xml; charset=3DISO-8859-1 Content-Transfer-Encoding: binary this is a test file. --PoNK69pnchJKwVLDEQ-phInJ_mC8R6e95M7OP--=20 Here=E2=80=99s the request sent from the browser (accepted) Header part: Host=20 User-AgentMozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:83.161.120.155) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)Accept text/html,application/xhtml+xml,application/xml;q=3D0.9,/;q=3D0.8Accept-Lan= guageen-us,en;q=3D0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=3D0.7,*;q=3D0.7 Keep-Alive 300 Connection keep-alive Referer https://www.xxxxxxxx Proxy-AuthorizationBasic Y2hlbndlYTpJYW1maWxlMA=3D=3D Body part: Content-Type: multipart/form-data; boundary=3D---------------------------41184676334 Content-Length: 651 -----------------------------41184676334 Content-Disposition: form-data; name=3D"file"; filename=3D"testfile.xfd" Content-Type: application/vnd.adobe.xfd+xml this is a test file. -----------------------------41184676334 Content-Disposition: form-data; name=3D"BulkSingleFlag" Single -----------------------------41184676334-- Any suggestions would be greatly appreciated. One thing I noticed is that the browser sent the lines below in the beginning of the body and HttpClien= t sent them as part of the header. Could that be a problem? If yes, how shoul= d I fix the behavior? Content-Type: multipart/form-data; boundary=3D---------------------------41184676334 Content-Length: 651 Here's the related source code: PostMethod request =3D new PostMethod(uri); FilePart filePart =3D createFilePart(fileUpload); Part[] parts =3D {new StringPart("BulkSingleFlag", "Single"), filePart}; =20 request.setRequestEntity(new MultipartRequestEntity(parts, request.getParams())); int httpResponseCode =3D httpClient.executeMethod(request); Thanks.=20 --=20 View this message in context: http://www.nabble.com/HttpClient-MultiPart-fi= le-upload-getting-rejected-tp25703852p25703852.html Sent from the HttpClient-User mailing list lynnalexis@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 01:48:19 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 29253 invoked from network); 5 Oct 2009 01:48:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 01:48:19 -0000 Received: (qmail 96038 invoked by uid 500); 5 Oct 2009 01:48:18 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 95955 invoked by uid 500); 5 Oct 2009 01:48:18 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 95945 invoked by uid 99); 5 Oct 2009 01:48:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 01:48:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO CAS01.apps4rent.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 05 Oct 2009 01:48:09 +0000 Received: from EXMBX01.apps4rent.net ([83.161.120.155]) by cas01.apps4rent.net ([83.161.120.155]) with mapi; Sun, 4 Oct 2009 18:47:48 -0700 From: Douglas Ferguson <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Date: Sun, 4 Oct 2009 18:47:46 -0700 Subject: Cookie rejected Thread-Topic: Cookie rejected Thread-Index: AcpFXdch8xf+8zioSMO37mimqOYxnA== Message-ID: <lynnalexis@example.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org I"m using HttpClient from apache commons I get of bunch of these warnings in my logs. I could set HttpmethodBase to INFO but I'd be worried that I'd loose =20 some useful information. Is there something else I could do to avoid these messages? Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - =20 Cookie rejected: " --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 09:22:28 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 25109 invoked from network); 5 Oct 2009 09:22:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 09:22:28 -0000 Received: (qmail 98926 invoked by uid 500); 5 Oct 2009 09:22:27 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 98846 invoked by uid 500); 5 Oct 2009 09:22:27 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 98836 invoked by uid 99); 5 Oct 2009 09:22:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 09:22:26 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-ew0-f214.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 09:22:17 +0000 Received: by ewy10 with SMTP id 10so2329506ewy.33 for <lynnalexis@example.com>; Mon, 05 Oct 2009 02:21:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=zdfWg7YZizjDivIrHC6XZEcOmlNAoM77N8sjK3femTQ=; b=Bh6+FnuqEtq6QNu4gOYLFI5nHOwIaYyZAlzwty9NH8DOx50g+M7ABNcepiiiQQJsIb KdkVQpsJsa3qHutXsUjAvDocig57ZG3lDjp1XVFYG/Tsg6G0ZQXzveAaBbriJcvrlYg3 Tr2QCNBNB2sdKYEdKzFPCr+MqAfBfBfJAN2AU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=icu/N/BCLZvq7e9JAG0OStCshl7OGMJAeHrsbGM9q+d7WwgL1WEKPe/e4FuSZ2nASm WW2ZViW7tsYvKB466p9xEHKaOa3v0/CjPEOgzF/55fIGE+bXkeGsmU70IXEdDmf+UTKE 3FVmICUsu+lNYdUtWbzY2KzmfqPm/ydV6qvCw= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id o19mr999989web.152.1254734517421; Mon, 05 Oct 2009 02:21:57 -0700 (PDT) In-Reply-To: <lynnalexis@example.com> References: <lynnalexis@example.com> Date: Mon, 5 Oct 2009 10:21:57 +0100 Message-ID: <lynnalexis@example.com> Subject: Re: Cookie rejected From: sebb <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: > I"m using HttpClient from apache commons > > I get of bunch of these warnings in my logs. > > I could set HttpmethodBase to INFO but I'd be worried that I'd loose > some useful information. > Is there something else I could do to avoid these messages? > > Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - > Cookie rejected: " FInd out why the cookie is being rejected, and either fix the cookie to be compliant, or configure HttpClient to use a cookie policy that allows the cookie. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lynnalexis@example.com > For additional commands, e-mail: lynnalexis@example.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 14:13:00 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 92924 invoked from network); 5 Oct 2009 14:12:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 14:12:59 -0000 Received: (qmail 79728 invoked by uid 500); 5 Oct 2009 14:12:59 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 79647 invoked by uid 500); 5 Oct 2009 14:12:59 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 79637 invoked by uid 99); 5 Oct 2009 14:12:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 14:12:59 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO CAS01.apps4rent.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 05 Oct 2009 14:12:48 +0000 Received: from EXMBX01.apps4rent.net ([83.161.120.155]) by cas01.apps4rent.net ([83.161.120.155]) with mapi; Mon, 5 Oct 2009 07:12:05 -0700 From: Douglas Ferguson <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Date: Mon, 5 Oct 2009 07:12:03 -0700 Subject: Re: Cookie rejected Thread-Topic: Cookie rejected Thread-Index: AcpFxdETiQpwmu7iSw+XgUnZpFHAVA== Message-ID: <lynnalexis@example.com> References: <lynnalexis@example.com> <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hmm.. Maybe I should be more explicit. Here's the warning: > Oct 05 09:13:47 WARN [pool-2-thread-16] httpclient.HttpMethodBase - =20 > Cookie rejected: "$Version=3D0; =20 > _twitter_sess=20 > =3DBAh7CjoRdHJhbnNfcHJvbXB0MDoOcmV0dXJuX3RvIh5odHRwOi8vdHdpdHRl=20 > %250Aci5jb20vamJuaW5kOgxjc3JmX2lkIiUxNmI1MDIwZjk5ZDY4NDg3OWZhZTIz=20 > %250AMWY2M2I2ZWQxMjoHaWQiJTQ4YmM1NmU2Nzc1ZWYwZWY1ZDVkMGFhMGMxYjQw=20 > %250AMjI2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hI=20 > %250AYXNoewAGOgpAdXNlZHsA--2cf7d8d6a5a619808fe1676a801b0ecfc8cc2aec; =20 > $Path=3D/; $Domain=3D.twitter.com". Illegal domain attribute =20 > ".twitter.com". Domain of origin: "twitter.com" I doubt I'll get twitter to change there page. :) How would I write a policy that dealt with this? D/ On Oct 5, 2009, at 4:21 AM, sebb wrote: > On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: >> I"m using HttpClient from apache commons >> >> I get of bunch of these warnings in my logs. >> >> I could set HttpmethodBase to INFO but I'd be worried that I'd loose >> some useful information. >> Is there something else I could do to avoid these messages? >> >> Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - >> Cookie rejected: " > > FInd out why the cookie is being rejected, and either fix the cookie > to be compliant, or configure HttpClient to use a cookie policy that > allows the cookie. > >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: lynnalexis@example.com >> For additional commands, e-mail: lynnalexis@example.com >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lynnalexis@example.com > For additional commands, e-mail: lynnalexis@example.com > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 15:18:25 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 11380 invoked from network); 5 Oct 2009 15:18:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 15:18:24 -0000 Received: (qmail 83883 invoked by uid 500); 5 Oct 2009 15:18:24 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 83838 invoked by uid 500); 5 Oct 2009 15:18:24 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 83828 invoked by uid 99); 5 Oct 2009 15:18:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 15:18:24 +0000 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 15:18:14 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <lynnalexis@example.com>) id 1MupJx-0002OE-8h for lynnalexis@example.com; Mon, 05 Oct 2009 08:17:53 -0700 Message-ID: <lynnalexis@example.com> Date: Mon, 5 Oct 2009 08:17:53 -0700 (PDT) From: ghanchakkar <lynnalexis@example.com> To: lynnalexis@example.com Subject: Re: Not able to upload bigger file (max size 4kb successful) In-Reply-To: <lynnalexis@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: lynnalexis@example.com References: <lynnalexis@example.com> <lynnalexis@example.com> X-Virus-Checked: Checked by ClamAV on apache.org olegk Thanks for your previous reply. It has been long that I am facing this issue, and not able to find any solution to this. Iplanet team has come back asking me to fix httpclient because internet explorer is successfully able to upload any size file to same i-planet web server without any issues, but my httpclient is getting exception (as described in my previous email) from server because server is closing connection. Can you suggest why i.e. is able to upload files with any file size without any issues and httpclient not? any place I should look at the code ? or anything else that comes in your mind ? Manoj olegk wrote: > > ghanchakkar wrote: >> I am using httpclient 3.1 with jre 1.5_15. I am able to post https >> request >> and able to get replys from iplanet web server with no issues, except >> when I >> try to upload file having size from than 9kb. Here is the log. >> >> Note: It seems connection close occurs at one particular point of the >> file >> but when I open the file there is no special chars or anything of that >> sort >> at that point of the file. Also note that this happens with every file no >> matter what the contents are. >> >> here is the log >> > > ... > >> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:404 [ClientId:] >> Closing the connection. >> 14:25:16.915 DEBUG [main] HttpConnection.java:1148 [ClientId:] >> enter HttpConnection.close() >> 14:25:16.915 DEBUG [main] HttpConnection.java:1215 [ClientId:] >> enter HttpConnection.closeSockedAndStreams() >> 14:25:16.915 INFO [main] HttpMethodDirector.java:439 [ClientId:] >> I/O exception (java.net.SocketException) caught when processing request: >> Software caused connection abort: socket write error >> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:443 [ClientId:] >> Software caused connection abort: socket write error >> java.net.SocketException: Software caused connection abort: socket write >> error >> at java.net.SocketOutputStream.socketWrite0(Native Method) >> at java.net.SocketOutputStream.socketWrite(Unknown Source) >> at java.net.SocketOutputStream.write(Unknown Source) > > > The exception has been caused by the server shutting down the connection > prematurely most likely due to a error or configuration issue on the > server side. This has nothing to do with HttpClient. > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lynnalexis@example.com > For additional commands, e-mail: lynnalexis@example.com > > > -- View this message in context: http://www.nabble.com/Not-able-to-upload-bigger-file-%28max-size-4kb-successful%29-tp23548792p25752702.html Sent from the HttpClient-User mailing list lynnalexis@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 18:26:26 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 74793 invoked from network); 5 Oct 2009 18:26:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 18:26:26 -0000 Received: (qmail 86188 invoked by uid 500); 5 Oct 2009 18:26:25 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 86110 invoked by uid 500); 5 Oct 2009 18:26:25 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 86100 invoked by uid 99); 5 Oct 2009 18:26:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 18:26:25 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO prxy.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 18:26:13 +0000 X-Scanned-By: RAE MPP/ClamAV http://raeinternet.com/mpp X-Scanned-By: This message was scanned by MPP Free Edition (www.messagepartners.com)! Received: from [83.161.120.155] (account lynnalexis@example.com HELO [83.161.120.155]) by prxy.net (CommuniGate Pro SMTP 4.2.10) with ESMTP id 116224750 for lynnalexis@example.com; Mon, 05 Oct 2009 11:23:55 -0700 Message-Id: <lynnalexis@example.com> From: Ken Krugler <lynnalexis@example.com> To: "HttpClient User Discussion" <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Content-Type: multipart/alternative; boundary=Apple-Mail-7--565743437 Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Not able to upload bigger file (max size 4kb successful) Date: Mon, 5 Oct 2009 11:20:47 -0700 References: <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-7--565743437 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On Oct 5, 2009, at 8:17am, ghanchakkar wrote: > > olegk > Thanks for your previous reply. > It has been long that I am facing this issue, and not able to find any > solution to this. Iplanet team has come back asking me to fix > httpclient > because internet explorer is successfully able to upload any size > file to > same i-planet web server without any issues, but my httpclient is > getting > exception (as described in my previous email) from server because > server is > closing connection. > Can you suggest why i.e. is able to upload files with any file size > without > any issues and httpclient not? any place I should look at the code ? > or > anything else that comes in your mind ? I think part of the issue here is that Oleg & the HttpClient community in general is more focused on HttpClient 4.0, versus the legacy 3.1 client. So depending on the size/complexity of your HttpClient-related code base, the fastest way to get a solution might be to migrate to 4.0. -- Ken > > olegk wrote: >> >> ghanchakkar wrote: >>> I am using httpclient 3.1 with jre 1.5_15. I am able to post https >>> request >>> and able to get replys from iplanet web server with no issues, >>> except >>> when I >>> try to upload file having size from than 9kb. Here is the log. >>> >>> Note: It seems connection close occurs at one particular point of >>> the >>> file >>> but when I open the file there is no special chars or anything of >>> that >>> sort >>> at that point of the file. Also note that this happens with every >>> file no >>> matter what the contents are. >>> >>> here is the log >>> >> >> ... >> >>> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:404 [ClientId:] >>> Closing the connection. >>> 14:25:16.915 DEBUG [main] HttpConnection.java:1148 [ClientId:] >>> enter HttpConnection.close() >>> 14:25:16.915 DEBUG [main] HttpConnection.java:1215 [ClientId:] >>> enter HttpConnection.closeSockedAndStreams() >>> 14:25:16.915 INFO [main] HttpMethodDirector.java:439 [ClientId:] >>> I/O exception (java.net.SocketException) caught when processing >>> request: >>> Software caused connection abort: socket write error >>> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:443 [ClientId:] >>> Software caused connection abort: socket write error >>> java.net.SocketException: Software caused connection abort: socket >>> write >>> error >>> at java.net.SocketOutputStream.socketWrite0(Native Method) >>> at java.net.SocketOutputStream.socketWrite(Unknown Source) >>> at java.net.SocketOutputStream.write(Unknown Source) >> >> >> The exception has been caused by the server shutting down the >> connection >> prematurely most likely due to a error or configuration issue on the >> server side. This has nothing to do with HttpClient. >> >> Oleg -------------------------- Ken Krugler TransPac Software, Inc. <http://www.transpac.com> +1-610-470-8587 --Apple-Mail-7--565743437-- From httpclient-userslynnalexis@example.com Mon Oct 05 19:46:55 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 20328 invoked from network); 5 Oct 2009 19:46:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 19:46:55 -0000 Received: (qmail 57183 invoked by uid 500); 5 Oct 2009 19:46:54 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 57144 invoked by uid 500); 5 Oct 2009 19:46:54 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 57134 invoked by uid 99); 5 Oct 2009 19:46:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 19:46:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-ew0-f205.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 19:46:43 +0000 Received: by ewy1 with SMTP id 1so2837224ewy.10 for <lynnalexis@example.com>; Mon, 05 Oct 2009 12:45:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=KkKJvq28G1oisFBnpG62m2oXO2zflEX3WO1wV8unC6c=; b=jrhTEXb84ZihDgvB17iJW5zd2wvIkar1rN5v7I8tD1KO9nHPrXLVLPeqgWs6oNLvvT o0M76sF7zfh6oyppUqH3LLAg0KyOEgHOMwF9bBJR6lVvJvmb8cOcxZpc65GU0/odXOLE Torhf2zcpvI1/dQZWACXlzy96yNF3MO2cxLKk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=n99UrjvF2kLCdhte/8GWbcqsA0Ko2iQNn0yE8jmYlgbLF/7ivviZtm2cFa0lwFihob bOUHASoYSD0AzpT+VX5AXoXkwupRyCggH2dIcG/ZxRTStMGuwGJv+e9fY5K/rx2Cu0/K Q9S7BILRWDT4dj4hPSSf+sbQjIM3ho+MPlnnI= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id v58mr97375wee.40.1254771922712; Mon, 05 Oct 2009 12:45:22 -0700 (PDT) In-Reply-To: <lynnalexis@example.com> References: <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> Date: Mon, 5 Oct 2009 20:45:22 +0100 Message-ID: <lynnalexis@example.com> Subject: Re: Cookie rejected From: sebb <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: > Hmm.. > > Maybe I should be more explicit. > > Here's the warning: > > > Oct 05 09:13:47 WARN [pool-2-thread-16] httpclient.HttpMethodBase - > > Cookie rejected: "$Version=0; > > _twitter_sess > > =BAh7CjoRdHJhbnNfcHJvbXB0MDoOcmV0dXJuX3RvIh5odHRwOi8vdHdpdHRl > > %250Aci5jb20vamJuaW5kOgxjc3JmX2lkIiUxNmI1MDIwZjk5ZDY4NDg3OWZhZTIz > > %250AMWY2M2I2ZWQxMjoHaWQiJTQ4YmM1NmU2Nzc1ZWYwZWY1ZDVkMGFhMGMxYjQw > > %250AMjI2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hI > > %250AYXNoewAGOgpAdXNlZHsA--2cf7d8d6a5a619808fe1676a801b0ecfc8cc2aec; > > $Path=/; $Domain=.twitter.com". Illegal domain attribute > > ".twitter.com". Domain of origin: "twitter.com" > > > I doubt I'll get twitter to change there page. :) > > How would I write a policy that dealt with this? What policy are you currently using? Have you tried all the other policies that are provided? > > D/ > > > > On Oct 5, 2009, at 4:21 AM, sebb wrote: > > > On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: > >> I"m using HttpClient from apache commons > >> > >> I get of bunch of these warnings in my logs. > >> > >> I could set HttpmethodBase to INFO but I'd be worried that I'd loose > >> some useful information. > >> Is there something else I could do to avoid these messages? > >> > >> Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - > >> Cookie rejected: " > > > > FInd out why the cookie is being rejected, and either fix the cookie > > to be compliant, or configure HttpClient to use a cookie policy that > > allows the cookie. > > > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: lynnalexis@example.com > >> For additional commands, e-mail: lynnalexis@example.com > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: lynnalexis@example.com > > For additional commands, e-mail: lynnalexis@example.com > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lynnalexis@example.com > For additional commands, e-mail: lynnalexis@example.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 19:55:41 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 22451 invoked from network); 5 Oct 2009 19:55:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 19:55:41 -0000 Received: (qmail 82556 invoked by uid 500); 5 Oct 2009 19:55:41 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 82504 invoked by uid 500); 5 Oct 2009 19:55:41 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 82494 invoked by uid 99); 5 Oct 2009 19:55:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 19:55:41 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO zm2.synquad.nl) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 19:55:29 +0000 Received: from localhost (localhost [83.161.120.155]) by zm2.synquad.nl (Postfix) with ESMTP id 66535438FD for <lynnalexis@example.com>; Mon, 5 Oct 2009 21:54:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at X-Spam-Score: 1.121 X-Spam-Level: * Received: from zm2.synquad.nl ([83.161.120.155]) by localhost (zm2.synquad.nl [83.161.120.155]) (amavisd-new, port 10024) with ESMTP id iSYaj9LOG0-D for <lynnalexis@example.com>; Mon, 5 Oct 2009 21:54:28 +0200 (CEST) Received: from ernst.lan (ehnolte.xs4all.nl [83.161.120.155]) by zm2.synquad.nl (Postfix) with ESMTP id B47E4438EF for <lynnalexis@example.com>; Mon, 5 Oct 2009 21:54:28 +0200 (CEST) Message-Id: <lynnalexis@example.com> From: Ernst Nolte <lynnalexis@example.com> To: "HttpClient User Discussion" <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: Not able to upload bigger file (max size 4kb successful) Date: Mon, 5 Oct 2009 21:54:32 +0200 References: <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> X-Mailer: Apple Mail (2.936) X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Flag: NO X-Old-Spam-Status: No, score=1.121 tagged_above=-10 required=6.6 tests=[AWL=0.006, BAYES_00=-2.599, HELO_LH_HOME=3.714] Could you show your code and describe the context from which it is executed? On 5 Oct 2009, at 20:20, Ken Krugler wrote: > > On Oct 5, 2009, at 8:17am, ghanchakkar wrote: > >> >> olegk >> Thanks for your previous reply. >> It has been long that I am facing this issue, and not able to find >> any >> solution to this. Iplanet team has come back asking me to fix >> httpclient >> because internet explorer is successfully able to upload any size >> file to >> same i-planet web server without any issues, but my httpclient is >> getting >> exception (as described in my previous email) from server because >> server is >> closing connection. >> Can you suggest why i.e. is able to upload files with any file size >> without >> any issues and httpclient not? any place I should look at the >> code ? or >> anything else that comes in your mind ? > > I think part of the issue here is that Oleg & the HttpClient > community in general is more focused on HttpClient 4.0, versus the > legacy 3.1 client. > > So depending on the size/complexity of your HttpClient-related code > base, the fastest way to get a solution might be to migrate to 4.0. > > -- Ken > >> >> olegk wrote: >>> >>> ghanchakkar wrote: >>>> I am using httpclient 3.1 with jre 1.5_15. I am able to post https >>>> request >>>> and able to get replys from iplanet web server with no issues, >>>> except >>>> when I >>>> try to upload file having size from than 9kb. Here is the log. >>>> >>>> Note: It seems connection close occurs at one particular point of >>>> the >>>> file >>>> but when I open the file there is no special chars or anything of >>>> that >>>> sort >>>> at that point of the file. Also note that this happens with every >>>> file no >>>> matter what the contents are. >>>> >>>> here is the log >>>> >>> >>> ... >>> >>>> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:404 [ClientId:] >>>> Closing the connection. >>>> 14:25:16.915 DEBUG [main] HttpConnection.java:1148 [ClientId:] >>>> enter HttpConnection.close() >>>> 14:25:16.915 DEBUG [main] HttpConnection.java:1215 [ClientId:] >>>> enter HttpConnection.closeSockedAndStreams() >>>> 14:25:16.915 INFO [main] HttpMethodDirector.java:439 [ClientId:] >>>> I/O exception (java.net.SocketException) caught when processing >>>> request: >>>> Software caused connection abort: socket write error >>>> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:443 [ClientId:] >>>> Software caused connection abort: socket write error >>>> java.net.SocketException: Software caused connection abort: >>>> socket write >>>> error >>>> at java.net.SocketOutputStream.socketWrite0(Native Method) >>>> at java.net.SocketOutputStream.socketWrite(Unknown Source) >>>> at java.net.SocketOutputStream.write(Unknown Source) >>> >>> >>> The exception has been caused by the server shutting down the >>> connection >>> prematurely most likely due to a error or configuration issue on the >>> server side. This has nothing to do with HttpClient. >>> >>> Oleg > > -------------------------- > Ken Krugler > TransPac Software, Inc. > <http://www.transpac.com> > +1-610-470-8587 > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 20:43:45 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 37684 invoked from network); 5 Oct 2009 20:43:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 20:43:45 -0000 Received: (qmail 85947 invoked by uid 500); 5 Oct 2009 20:43:44 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 85890 invoked by uid 500); 5 Oct 2009 20:43:44 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 85880 invoked by uid 99); 5 Oct 2009 20:43:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 20:43:44 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO CAS01.apps4rent.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 05 Oct 2009 20:43:33 +0000 Received: from EXMBX01.apps4rent.net ([83.161.120.155]) by cas01.apps4rent.net ([83.161.120.155]) with mapi; Mon, 5 Oct 2009 13:43:12 -0700 From: Douglas Ferguson <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Date: Mon, 5 Oct 2009 13:43:11 -0700 Subject: Re: Cookie rejected Thread-Topic: Cookie rejected Thread-Index: AcpF/HSXjzfk/uNwTpCWzwzW3Qixvg== Message-ID: <lynnalexis@example.com> References: <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org I guess I'm using the default. I just generating a GetMethod and then running execute. D/ On Oct 5, 2009, at 2:45 PM, sebb wrote: > On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: >> Hmm.. >> >> Maybe I should be more explicit. >> >> Here's the warning: >> >>> Oct 05 09:13:47 WARN [pool-2-thread-16] httpclient.HttpMethodBase - >>> Cookie rejected: "$Version=3D0; >>> _twitter_sess >>> =3DBAh7CjoRdHJhbnNfcHJvbXB0MDoOcmV0dXJuX3RvIh5odHRwOi8vdHdpdHRl >>> %250Aci5jb20vamJuaW5kOgxjc3JmX2lkIiUxNmI1MDIwZjk5ZDY4NDg3OWZhZTIz >>> %250AMWY2M2I2ZWQxMjoHaWQiJTQ4YmM1NmU2Nzc1ZWYwZWY1ZDVkMGFhMGMxYjQw >>> %250AMjI2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hI >>> %250AYXNoewAGOgpAdXNlZHsA--2cf7d8d6a5a619808fe1676a801b0ecfc8cc2aec; >>> $Path=3D/; $Domain=3D.twitter.com". Illegal domain attribute >>> ".twitter.com". Domain of origin: "twitter.com" >> >> >> I doubt I'll get twitter to change there page. :) >> >> How would I write a policy that dealt with this? > > What policy are you currently using? > Have you tried all the other policies that are provided? > >> >> D/ >> >> >> >> On Oct 5, 2009, at 4:21 AM, sebb wrote: >> >>> On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: >>>> I"m using HttpClient from apache commons >>>> >>>> I get of bunch of these warnings in my logs. >>>> >>>> I could set HttpmethodBase to INFO but I'd be worried that I'd =20 >>>> loose >>>> some useful information. >>>> Is there something else I could do to avoid these messages? >>>> >>>> Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - >>>> Cookie rejected: " >>> >>> FInd out why the cookie is being rejected, and either fix the cookie >>> to be compliant, or configure HttpClient to use a cookie policy that >>> allows the cookie. >>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: lynnalexis@example.com >>>> For additional commands, e-mail: httpclient-users-=20 >>>> lynnalexis@example.com >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: lynnalexis@example.com >>> For additional commands, e-mail: lynnalexis@example.com >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: lynnalexis@example.com >> For additional commands, e-mail: lynnalexis@example.com >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lynnalexis@example.com > For additional commands, e-mail: lynnalexis@example.com > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Mon Oct 05 22:56:20 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 87354 invoked from network); 5 Oct 2009 22:56:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 5 Oct 2009 22:56:20 -0000 Received: (qmail 51739 invoked by uid 500); 5 Oct 2009 22:56:20 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 51715 invoked by uid 500); 5 Oct 2009 22:56:20 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 51705 invoked by uid 99); 5 Oct 2009 22:56:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 22:56:20 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-ew0-f205.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Oct 2009 22:56:09 +0000 Received: by ewy1 with SMTP id 1so3010140ewy.10 for <lynnalexis@example.com>; Mon, 05 Oct 2009 15:54:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=HKX8My2gRuZbMNhp8HNg0ZEmAfLMD0OHqJI+WRjYyi4=; b=da30kuGPE5dr1piUuXs+o64s4SIPSrHLaSAMO8I5fHh8LghRRiLPsQQMKGD+kLWBuG suQLRuD3Q6CwECt6TZWdvz0cjI6VnmLBC6iqjeVV8g92BzNP1A4V5N8+1Xs2GQ6tmVeW ZbqTA7M7wM4SgBCkvR0PzADqUoeC1XdpXDqMs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=WNk2V6KuloBUx5Teuiy799yP8PDjBxlzr4gwQp9ryeg8rJWr2wfjEqMl2iD8n8i1dY 5Au+1R6yRA3/RfBgPSosZs6JQEgV0oL9S/ZrL4hXSqwkFpUqSKlW8mzVwWseQoPoZdDb 048elhavq+YvRdaMmMO8+jkH2bNbHm0UyMLHs= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id b61mr143678web.91.1254783288262; Mon, 05 Oct 2009 15:54:48 -0700 (PDT) In-Reply-To: <lynnalexis@example.com> References: <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> Date: Mon, 5 Oct 2009 23:54:48 +0100 Message-ID: <lynnalexis@example.com> Subject: Re: Cookie rejected From: sebb <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org So - try using a different policy. See: http://hc.apache.org/httpclient-3.x/cookies.html On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: > I guess I'm using the default. > > I just generating a GetMethod and then running execute. > > > D/ > > > On Oct 5, 2009, at 2:45 PM, sebb wrote: > > > On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: > >> Hmm.. > >> > >> Maybe I should be more explicit. > >> > >> Here's the warning: > >> > >>> Oct 05 09:13:47 WARN [pool-2-thread-16] httpclient.HttpMethodBase - > >>> Cookie rejected: "$Version=0; > >>> _twitter_sess > >>> =BAh7CjoRdHJhbnNfcHJvbXB0MDoOcmV0dXJuX3RvIh5odHRwOi8vdHdpdHRl > >>> %250Aci5jb20vamJuaW5kOgxjc3JmX2lkIiUxNmI1MDIwZjk5ZDY4NDg3OWZhZTIz > >>> %250AMWY2M2I2ZWQxMjoHaWQiJTQ4YmM1NmU2Nzc1ZWYwZWY1ZDVkMGFhMGMxYjQw > >>> %250AMjI2IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hI > >>> %250AYXNoewAGOgpAdXNlZHsA--2cf7d8d6a5a619808fe1676a801b0ecfc8cc2aec; > >>> $Path=/; $Domain=.twitter.com". Illegal domain attribute > >>> ".twitter.com". Domain of origin: "twitter.com" > >> > >> > >> I doubt I'll get twitter to change there page. :) > >> > >> How would I write a policy that dealt with this? > > > > What policy are you currently using? > > Have you tried all the other policies that are provided? > > > >> > >> D/ > >> > >> > >> > >> On Oct 5, 2009, at 4:21 AM, sebb wrote: > >> > >>> On 05/10/2009, Douglas Ferguson <lynnalexis@example.com> wrote: > >>>> I"m using HttpClient from apache commons > >>>> > >>>> I get of bunch of these warnings in my logs. > >>>> > >>>> I could set HttpmethodBase to INFO but I'd be worried that I'd > >>>> loose > >>>> some useful information. > >>>> Is there something else I could do to avoid these messages? > >>>> > >>>> Oct 04 20:49:22 WARN [pool-2-thread-5] httpclient.HttpMethodBase - > >>>> Cookie rejected: " > >>> > >>> FInd out why the cookie is being rejected, and either fix the cookie > >>> to be compliant, or configure HttpClient to use a cookie policy that > >>> allows the cookie. > >>> > >>>> > >>>> > >>>> > >>>> --------------------------------------------------------------------- > >>>> To unsubscribe, e-mail: lynnalexis@example.com > >>>> For additional commands, e-mail: httpclient-users- > >>>> lynnalexis@example.com > >>>> > >>>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: lynnalexis@example.com > >>> For additional commands, e-mail: lynnalexis@example.com > >>> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: lynnalexis@example.com > >> For additional commands, e-mail: lynnalexis@example.com > >> > >> > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: lynnalexis@example.com > > For additional commands, e-mail: lynnalexis@example.com > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: lynnalexis@example.com > For additional commands, e-mail: lynnalexis@example.com > > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Tue Oct 06 03:16:05 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 50092 invoked from network); 6 Oct 2009 03:16:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Oct 2009 03:16:05 -0000 Received: (qmail 48804 invoked by uid 500); 6 Oct 2009 03:16:05 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 48722 invoked by uid 500); 6 Oct 2009 03:16:05 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 48712 invoked by uid 99); 6 Oct 2009 03:16:05 -0000 Received: from Unknown (HELO hercules.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 03:16:05 +0000 X-ASF-Spam-Status: No, hits=-0.3 required=5.0 tests=BAYES_00,FORGED_YAHOO_RCVD X-Spam-Check-By: apache.org Received-SPF: pass (hercules.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 03:15:54 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <lynnalexis@example.com>) id 1Mv0WT-0006ai-Ii for lynnalexis@example.com; Mon, 05 Oct 2009 20:15:33 -0700 Message-ID: <lynnalexis@example.com> Date: Mon, 5 Oct 2009 20:15:33 -0700 (PDT) From: tyweed <lynnalexis@example.com> To: lynnalexis@example.com Subject: Apache's HttpClient don't want URL Encoding any ideas how I can bypass? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: lynnalexis@example.com I have an application i'm building that needs to send requests that do not URLEncode characters in the URL. I have tried everything I can think of to bypass the URL Encoding and have had no luck. Is there any idea or work around anyone can offer? I thought about getting the src and altering it but it turned out to be more difficult than I anticipated. I have heard that HTTP Core is an option but i'd rather go that route as last case scenario. Any ideas any help would be very appreciated! -- View this message in context: http://www.nabble.com/Apache%27s-HttpClient-don%27t-want-URL-Encoding-any-ideas-how-I-can-bypass--tp25762297p25762297.html Sent from the HttpClient-User mailing list lynnalexis@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Tue Oct 06 12:40:37 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 75634 invoked from network); 6 Oct 2009 12:40:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 6 Oct 2009 12:40:37 -0000 Received: (qmail 80325 invoked by uid 500); 6 Oct 2009 12:40:37 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 80275 invoked by uid 500); 6 Oct 2009 12:40:37 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 80255 invoked by uid 99); 6 Oct 2009 12:40:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 12:40:36 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO ok2cons2.nine.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 12:40:26 +0000 Received: from [83.161.120.155] (77-58-234-86.dclient.hispeed.ch [83.161.120.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ok2cons2.nine.ch (Postfix) with ESMTPSA id 369A14BA3E1 for <lynnalexis@example.com>; Tue, 6 Oct 2009 14:39:35 +0200 (CEST) Message-ID: <lynnalexis@example.com> Date: Tue, 06 Oct 2009 14:39:30 +0200 From: Oleg Kalnichevski <lynnalexis@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20090812) MIME-Version: 1.0 To: HttpClient User Discussion <lynnalexis@example.com> Subject: Re: Not able to upload bigger file (max size 4kb successful) References: <lynnalexis@example.com> <lynnalexis@example.com> <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org ghanchakkar wrote: > olegk > Thanks for your previous reply. > It has been long that I am facing this issue, and not able to find any > solution to this. Iplanet team has come back asking me to fix httpclient > because internet explorer is successfully able to upload any size file to > same i-planet web server without any issues, Great. Likewise, I can easily advise Iplanet team to fix Iplanet, because HttpClient is know to work well with other, better maintained, HTTP servers. but my httpclient is getting > exception (as described in my previous email) from server because server is > closing connection. > Can you suggest why i.e. is able to upload files with any file size without > any issues and httpclient not? There are lots of reasons for that. HttpClient may generate slightly different HTTP messages than IE, and iPlanet may react differently to different message compositions. (1) consider upgrading to HttpClient 4.0 first (2) capture HTTP messages generated by IE (3) capture HTTP messages generated by HttpClient (4) compare them (5) tweak HttpClient to generate HTTP more compatible with those generated by IE Oleg any place I should look at the code ? or > anything else that comes in your mind ? > > Manoj > > > olegk wrote: >> ghanchakkar wrote: >>> I am using httpclient 3.1 with jre 1.5_15. I am able to post https >>> request >>> and able to get replys from iplanet web server with no issues, except >>> when I >>> try to upload file having size from than 9kb. Here is the log. >>> >>> Note: It seems connection close occurs at one particular point of the >>> file >>> but when I open the file there is no special chars or anything of that >>> sort >>> at that point of the file. Also note that this happens with every file no >>> matter what the contents are. >>> >>> here is the log >>> >> ... >> >>> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:404 [ClientId:] >>> Closing the connection. >>> 14:25:16.915 DEBUG [main] HttpConnection.java:1148 [ClientId:] >>> enter HttpConnection.close() >>> 14:25:16.915 DEBUG [main] HttpConnection.java:1215 [ClientId:] >>> enter HttpConnection.closeSockedAndStreams() >>> 14:25:16.915 INFO [main] HttpMethodDirector.java:439 [ClientId:] >>> I/O exception (java.net.SocketException) caught when processing request: >>> Software caused connection abort: socket write error >>> 14:25:16.915 DEBUG [main] HttpMethodDirector.java:443 [ClientId:] >>> Software caused connection abort: socket write error >>> java.net.SocketException: Software caused connection abort: socket write >>> error >>> at java.net.SocketOutputStream.socketWrite0(Native Method) >>> at java.net.SocketOutputStream.socketWrite(Unknown Source) >>> at java.net.SocketOutputStream.write(Unknown Source) >> >> The exception has been caused by the server shutting down the connection >> prematurely most likely due to a error or configuration issue on the >> server side. This has nothing to do with HttpClient. >> >> Oleg >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: lynnalexis@example.com >> For additional commands, e-mail: lynnalexis@example.com >> >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Wed Oct 07 15:31:26 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 89544 invoked from network); 7 Oct 2009 15:31:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 7 Oct 2009 15:31:24 -0000 Received: (qmail 65457 invoked by uid 500); 7 Oct 2009 15:31:23 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 65410 invoked by uid 500); 7 Oct 2009 15:31:23 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 65400 invoked by uid 99); 7 Oct 2009 15:31:23 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 15:31:23 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO ok2cons2.nine.ch) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Oct 2009 15:31:12 +0000 Received: from [83.161.120.155] (77-58-234-86.dclient.hispeed.ch [83.161.120.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ok2cons2.nine.ch (Postfix) with ESMTPSA id 6A7E14BA3E1 for <lynnalexis@example.com>; Wed, 7 Oct 2009 17:30:52 +0200 (CEST) Message-ID: <lynnalexis@example.com> Date: Wed, 07 Oct 2009 17:30:45 +0200 From: Oleg Kalnichevski <lynnalexis@example.com> User-Agent: Thunderbird 83.161.120.155 (Windows/20090812) MIME-Version: 1.0 To: HttpClient User Discussion <lynnalexis@example.com> Subject: Re: Apache's HttpClient don't want URL Encoding any ideas how I can bypass? References: <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org tyweed wrote: > I have an application i'm building that needs to send requests that do not > URLEncode characters in the URL. I have tried everything I can think of to > bypass the URL Encoding and have had no luck. Is there any idea or work > around anyone can offer? I thought about getting the src and altering it but > it turned out to be more difficult than I anticipated. I have heard that > HTTP Core is an option but i'd rather go that route as last case scenario. > > Any ideas any help would be very appreciated! HttpClient 4.0 relies on the standard java.net.URI class to represent request URIs. Therefore HttpClient can work with any URI that is accepted by the java.net.URI parser as a valid one. If all you want is have to a different formatting for URIs, there are several extension points one can use to override the standard formatting routine with a custom one: a custom LineFormatter impl would be one possibility; another one would be overriding the #getRequestLine() method of the HttpRequestBase class. Hope this helps Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Thu Oct 08 03:58:32 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 67943 invoked from network); 8 Oct 2009 03:58:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 8 Oct 2009 03:58:31 -0000 Received: (qmail 50144 invoked by uid 500); 8 Oct 2009 03:58:31 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 50093 invoked by uid 500); 8 Oct 2009 03:58:31 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 50081 invoked by uid 99); 8 Oct 2009 03:58:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 03:58:31 +0000 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=FORGED_YAHOO_RCVD,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 03:58:21 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <lynnalexis@example.com>) id 1Mvk8e-0003xz-1O for lynnalexis@example.com; Wed, 07 Oct 2009 20:58:00 -0700 Message-ID: <lynnalexis@example.com> Date: Wed, 7 Oct 2009 20:58:00 -0700 (PDT) From: cllai <lynnalexis@example.com> To: lynnalexis@example.com Subject: Re: reading entity bytes from a HttpEntityEnclosingRequest in case of large content size In-Reply-To: <lynnalexis@example.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: lynnalexis@example.com References: <lynnalexis@example.com> X-Virus-Checked: Checked by ClamAV on apache.org hi, i m working on same type of system as u. i have no idea how i can redirect my uploaded file in HttpClient to target server. And how the target server store the file into hardisk? -- View this message in context: http://www.nabble.com/reading-entity-bytes-from-a-HttpEntityEnclosingRequest-in-case-of-large-content-size-tp24996302p25798013.html Sent from the HttpClient-User mailing list lynnalexis@example.com. --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Thu Oct 08 09:17:39 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 45471 invoked from network); 8 Oct 2009 09:17:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 8 Oct 2009 09:17:39 -0000 Received: (qmail 56277 invoked by uid 500); 8 Oct 2009 09:17:38 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 56223 invoked by uid 500); 8 Oct 2009 09:17:38 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 56213 invoked by uid 99); 8 Oct 2009 09:17:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 09:17:38 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO g1t0026.austin.hp.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 09:17:26 +0000 Received: from G1W0400.americas.hpqcorp.net (g1w0400.americas.hpqcorp.net [83.161.120.155]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by g1t0026.austin.hp.com (Postfix) with ESMTPS id A6CCFC311 for <lynnalexis@example.com>; Thu, 8 Oct 2009 09:17:05 +0000 (UTC) Received: from G4W0659.americas.hpqcorp.net (83.161.120.155) by G1W0400.americas.hpqcorp.net (83.161.120.155) with Microsoft SMTP Server (TLS) id 83.161.120.155; Thu, 8 Oct 2009 09:16:27 +0000 Received: from GVW1162EXB.americas.hpqcorp.net ([83.161.120.155]) by G4W0659.americas.hpqcorp.net ([83.161.120.155]) with mapi; Thu, 8 Oct 2009 09:16:27 +0000 From: "Kalbagilmath, Vishwanath (Communication & Media Solution)" <lynnalexis@example.com> To: "lynnalexis@example.com" <lynnalexis@example.com> Date: Thu, 8 Oct 2009 09:16:24 +0000 Subject: parsing uri problem with httpclient 3.1 Thread-Topic: parsing uri problem with httpclient 3.1 Thread-Index: AcpHL1ajNZCkUDBMRl+r6ehObxWMRQAyIRGw Message-ID: <lynnalexis@example.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_2118D41AB77C214BBF7D2330CD977BCF28F86BEF90GVW1162EXBame_" MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_2118D41AB77C214BBF7D2330CD977BCF28F86BEF90GVW1162EXBame_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello, I am facing URI parse problem with httpclient 3.1. The URI I have is ("http= ://83.161.120.155/selection.php?type[]=3DOFF&type[]=3DPA"). After going through 3.1 code (URI.java), I notice that, in parseUriRequest(= ) method, the query is validate aganists uric which does not contain "[" an= d "]" characters. The validation is newly addition in 3.1 version, this cha= nge is to align with RFC? If yes, what is the way out for uri having "[]"? This works fine in httpclient 3.0. Thanks in adv for the answer. regards --ViK --_000_2118D41AB77C214BBF7D2330CD977BCF28F86BEF90GVW1162EXBame_-- From httpclient-userslynnalexis@example.com Thu Oct 08 17:26:01 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 93158 invoked from network); 8 Oct 2009 17:26:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 8 Oct 2009 17:26:01 -0000 Received: (qmail 51463 invoked by uid 500); 8 Oct 2009 17:26:01 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 51437 invoked by uid 500); 8 Oct 2009 17:26:01 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 51427 invoked by uid 99); 8 Oct 2009 17:26:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 17:26:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lynnalexis@example.com designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-fx0-f221.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 17:25:51 +0000 Received: by fxm21 with SMTP id 21so5184560fxm.33 for <lynnalexis@example.com>; Thu, 08 Oct 2009 10:25:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=9zhtudDigU1Z7hRoWR3uF32PtbpuFU24TzRVCqEQ3Pg=; b=M9nYndJCT2mBTJMDG/MWnWWrJJ0VWvjT5I5JG+vy7wECaf732Jg5i7lU+Kr43uljl5 b7DiVeLx2rUhXGUFxGgZPluyyBngXc9FAKoCqSQJp/f0wcLudWuKkOGYBl0bvzK3Kiqa H0SXWClIuX4lC1GW06wPg7kr5OzCTX/3uIQ40= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=GvTQS7ryK2w43SJOWueE6/xPdThDrSawa728rJQEQIjVdNnwerJnylUE53BolaHhOz NdbjRjnP8MmtsIhXyIvnNYtu/vuudGFl/bNTeyiBHKDYq3dY15gqO6qMETBqTc/Utocd tQPQeuLChP8NUjr7ADrGorbFkgVDb9KcwvYXQ= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id w1mr486142fak.46.1255022731253; Thu, 08 Oct 2009 10:25:31 -0700 (PDT) Date: Thu, 8 Oct 2009 12:25:31 -0500 Message-ID: <lynnalexis@example.com> Subject: getResponseBodyAsStream vs. getResponseBodyAsString From: Randy Paries <lynnalexis@example.com> To: lynnalexis@example.com Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org I was wondering if someone could give me insight on when to use getResponseBodyAsStream vs. getResponseBodyAsString The getResponseBodyAsString seems to be very straight forward but would like to understand the best scenarios for each thanks Randy --------------------------------------------------------------------- To unsubscribe, e-mail: lynnalexis@example.com For additional commands, e-mail: lynnalexis@example.com From httpclient-userslynnalexis@example.com Thu Oct 08 17:42:39 2009 Return-Path: <httpclient-userslynnalexis@example.com> Delivered-To: lynnalexis@example.com Received: (qmail 97498 invoked from network); 8 Oct 2009 17:42:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 8 Oct 2009 17:42:39 -0000 Received: (qmail 81748 invoked by uid 500); 8 Oct 2009 17:42:37 -0000 Delivered-To: lynnalexis@example.com Received: (qmail 81702 invoked by uid 500); 8 Oct 2009 17:42:37 -0000 Mailing-List: contact lynnalexis@example.com; run by ezmlm Precedence: bulk List-Help: <mailto:lynnalexis@example.com> List-Unsubscribe: <mailto:lynnalexis@example.com> List-Post: <mailto:lynnalexis@example.com> List-Id: <httpclient-users.hc.apache.org> Reply-To: "HttpClient User Discussion" <lynnalexis@example.com> Delivered-To: mailing list lynnalexis@example.com Received: (qmail 81692 invoked by uid 99); 8 Oct 2009 17:42:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Oct 2009 17:42:37 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO CAS01.apps4rent.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 08 Oct 2009 17:42:28 +0000 Received: from EXMBX01.apps4rent.net ([83.161.120.155]) by cas01.apps4rent.net ([83.161.120.155]) with mapi; Thu, 8 Oct 2009 10:42:06 -0700 From: Douglas Ferguson <lynnalexis@example.com> To: HttpClient User Discussion <lynnalexis@example.com> Date: Thu, 8 Oct 2009 10:42:05 -0700 Subject: Re: getResponseBodyAsStream vs. getResponseBodyAsString Thread-Topic: getResponseBodyAsStream vs. getResponseBodyAsString Thread-Index: AcpIPqbbdTPza74eRKKwAR1HAIMFLw== Message-ID: <lynnalexis@example.com> References: <lynnalexis@example.com> In-Reply-To: <lynnalexis@example.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org It really depends on your usecase. getResponseBodyAsString will buffer the entire response
{'source': 'Apache Software Foundation Public Mail Archives'}