Return-Path: Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: (qmail 16308 invoked from network); 23 May 2008 21:03:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 May 2008 21:03:39 -0000 Received: (qmail 21208 invoked by uid 500); 23 May 2008 21:03:39 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 21188 invoked by uid 500); 23 May 2008 21:03:39 -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 21177 invoked by uid 99); 23 May 2008 21:03:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2008 14:03:39 -0700 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 dimi.chr@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 May 2008 21:02:47 +0000 Received: by ug-out-1314.google.com with SMTP id m3so855027uge.19 for ; Fri, 23 May 2008 14:03:10 -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:mime-version:content-type:content-transfer-encoding:content-disposition; bh=1cetfirZECnfh056+pyNVsR7riVzkMSQLaFzVcR0SJg=; b=FV1blov2aDgv7mEG8WV9BU7JCBEmnWz/PXWRjZeWCLW8jIeWALk1ixHRJLccgKrUpM5Kx9Vw7blMjOR3HohyJ/I1mazfUqczEVQK3U5tw6uMtCA8QDXg7l1ZJ9BVJdRvJl7bwGCeEG98AjlEyyjgJqWJkwTGttUq+puwh79UMuo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=FMKCGkjxMFCjUn0jAW+5ILmPBo8jy5TMwF2wsd3SH3Q3eR1/99tq39HMiBAb1Jg4K8PrUhQ0xzg2AFjrqYf6B6DzT1Mx2pzLugiB2mtaxPwdY16mI+1fGS3ygclTsoTYBU9rtVG9hN50kXcRcfIvaej1gKFTkt79KdA1n2AFziU= Received: by 10.78.189.5 with SMTP id m5mr98998huf.77.1211576589580; Fri, 23 May 2008 14:03:09 -0700 (PDT) Received: by 10.78.10.6 with HTTP; Fri, 23 May 2008 14:03:09 -0700 (PDT) Message-ID: Date: Fri, 23 May 2008 16:03:09 -0500 From: "Dimitrios Christodoulakis" To: httpclient-users@hc.apache.org Subject: difference between request headers and request params MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org 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. Do they have the same functionality for GET and POST requests? I mean does the server processes and responds differently to headers or parameters? 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