Return-Path: Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: (qmail 38710 invoked from network); 19 Jun 2008 22:02:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jun 2008 22:02:16 -0000 Received: (qmail 43039 invoked by uid 500); 19 Jun 2008 22:02:17 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 43018 invoked by uid 500); 19 Jun 2008 22:02:17 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 43006 invoked by uid 99); 19 Jun 2008 22:02:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jun 2008 15:02:17 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jun 2008 22:01:26 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1K9SCO-000436-PX for httpclient-users@hc.apache.org; Thu, 19 Jun 2008 15:01:44 -0700 Message-ID: <18019217.post@talk.nabble.com> Date: Thu, 19 Jun 2008 15:01:44 -0700 (PDT) From: David Gallardo To: httpclient-users@hc.apache.org Subject: Re: Message body in GET method? In-Reply-To: <19196d860806191452y25b3feb9u1a60c18c9af36548@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: david@gallardo.org References: <17994858.post@talk.nabble.com> <1213901043.7922.1.camel@ubuntu> <18016089.post@talk.nabble.com> <1213909015.7922.8.camel@ubuntu> <18018800.post@talk.nabble.com> <485AD2A2.3050305@apache.org> <18018948.post@talk.nabble.com> <19196d860806191452y25b3feb9u1a60c18c9af36548@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org Yes, I'm asking the latter question, how to do a retrieval based on a largish-entity--while trying to adhere to the semantics, idempotency, intention, etc. of HTTP. @D Sam Berlin wrote: > > >> So how else to do a retrieval? > > If you are asking how to do this in code -- I mentioned earlier on in > the thread, it's a very trivial thing to add. Simply make a new class > that extends HttpGet and implements HttpEntityEnclosingRequest (with a > name such as HttpEntityEnclosingGet), or extend > HttpEntityEnclosingRequestBase with a subclass whose getMethod returns > "GET". > > If you are asking how to do a retrieval based on a largish-entity... > I'm not sure. > > Sam > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org > For additional commands, e-mail: httpclient-users-help@hc.apache.org > > > -- View this message in context: http://www.nabble.com/Message-body-in-GET-method--tp17994858p18019217.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org