Return-Path: Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: (qmail 30927 invoked from network); 24 May 2008 14:04:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 May 2008 14:04:17 -0000 Received: (qmail 73111 invoked by uid 500); 24 May 2008 14:04:18 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 73087 invoked by uid 500); 24 May 2008 14:04:18 -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 73075 invoked by uid 99); 24 May 2008 14:04:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 May 2008 07:04:18 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dimi.chr@gmail.com designates 209.85.128.188 as permitted sender) Received: from [209.85.128.188] (HELO fk-out-0910.google.com) (209.85.128.188) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 24 May 2008 14:03:32 +0000 Received: by fk-out-0910.google.com with SMTP id z22so1089110fkz.6 for ; Sat, 24 May 2008 07:03:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=oWigaXJzNIEzs2nvXXgTTjsjA6DBpY2BvyFg2eXSJdU=; b=Lvsf/ilckg1zXRJGI1pTC8C46M7mwPWNDzGqQS/qIYRUhTOXNsFhIMqYCUk3uv0v44w/oGMuHbprW4FFK3912tWZSOkA/ixl3qxRnBqOO0NNzZX+b4YvzgYdXuQUKkeI6mgmRHuqOFHuHLUr82VBLutlgLPv6VCn4L+1ZxsV01Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=k0AA16dlypxSd1r1OwZKZogPDntLTH/FytB1wUaDAlKdIUbgn61tu4Ntb8tQUAGoxFNMzRyJYEm/vxZmCXrQjOjEWR4dRz6ElRty1Mf/BJAvn5y22ApCJKIV3eYVrjvzRAZY7at5UjOOuhBg+MK0vE/WMEczmYUwi8YbvPiKNxY= Received: by 10.78.121.2 with SMTP id t2mr33870huc.50.1211637827677; Sat, 24 May 2008 07:03:47 -0700 (PDT) Received: by 10.78.10.6 with HTTP; Sat, 24 May 2008 07:03:47 -0700 (PDT) Message-ID: Date: Sat, 24 May 2008 09:03:47 -0500 From: "Dimitrios Christodoulakis" To: "HttpClient User Discussion" Subject: Re: difference between request headers and request params In-Reply-To: <1211626801.7139.7.camel@ubuntu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1211626801.7139.7.camel@ubuntu> X-Virus-Checked: Checked by ClamAV on apache.org Thank you for your quick reply. That sure helps. As I keep working and practicing with HttpClient, I will post new questions. This seems like a very handy tool actually. On Sat, May 24, 2008 at 6:00 AM, Oleg Kalnichevski wrote: > On Fri, 2008-05-23 at 16:03 -0500, Dimitrios Christodoulakis wrote: >> Hello, I am a new user of HTTPClient and trying to learn how to use >> it. I have read the relevant primer and user guide but I am not sure >> what is the difference between headers and parameters. > > HTTP headers are elements of the HTTP request sent to the target server. > Parameters are merely attributes that affect the way HttpClient > functions. Parameters can apply to different aspects of HttpClient, not > just request messages. > > >> Do they have >> the same functionality for GET and POST requests? > > No, they do not > >> I mean does the >> server processes and responds differently to headers or parameters? >> > > No, it does not. The server is completely unaware of the parameters. > They are not a part of the HTTP protocol. > > Hope this helps > > Oleg > >> I am trying to set request headers with >> addRequestHeader("MyHeaderName", "MyHeaderValue"); and then after >> executing the method I print the headers like: >> >> Header[] reqheaders = authget.getRequestHeaders(); >> for (int i=1; i> System.out.println(reqheaders[i].getName().toString() +" = "+ >> reqheaders[i].getValue().toString()); >> } >> >> But no headers are displayed. >> >> Thanks for helping >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org >> For additional commands, e-mail: httpclient-users-help@hc.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org > For additional commands, e-mail: httpclient-users-help@hc.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org