Return-Path: Delivered-To: apmail-camel-dev-archive@www.apache.org Received: (qmail 36934 invoked from network); 24 Feb 2009 01:34:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Feb 2009 01:34:34 -0000 Received: (qmail 92427 invoked by uid 500); 24 Feb 2009 01:34:34 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 92409 invoked by uid 500); 24 Feb 2009 01:34:34 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 92398 invoked by uid 500); 24 Feb 2009 01:34:34 -0000 Delivered-To: apmail-activemq-camel-dev@activemq.apache.org Received: (qmail 92395 invoked by uid 99); 24 Feb 2009 01:34:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Feb 2009 17:34:34 -0800 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 email.wtam@gmail.com designates 209.85.217.163 as permitted sender) Received: from [209.85.217.163] (HELO mail-gx0-f163.google.com) (209.85.217.163) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Feb 2009 01:34:26 +0000 Received: by gxk7 with SMTP id 7so6452974gxk.14 for ; Mon, 23 Feb 2009 17:34:06 -0800 (PST) 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:content-transfer-encoding; bh=+LtvdGA5RnyV9E404bEUmaSt9wXZ7iDWRhy2pAZwAKY=; b=dTOM5Cxyz8Qg5vjW40G33hY8rQlFYNBNhJqlCgaf7YANumXrBnV+lExisEy6p9a1NO dapXwzcXJ5aS+BkOSgvMDEQYKqjNnsL5kZ6slfWtZ4PqsxKhC7GxuLhX185FjDLyQVEX VGC29Gj1jNJVXOH/fCNAMSH1OBsENcDWdYDZU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=PtMBRcGjlJlzwtQZvNP8hK+FdNpC58kwHqb07n6QKbVoQCDVq4tnLp0XGsEIBPdxw9 h91GWYDkJxq6xExd/mudLCwcWs0nepz0bMBAnAxThr6MxyczEt3zot5Xnh6c+Vv40G0E zAVdxzANicNGfPTf4tJrbFjxluxQJK/k5alZ0= MIME-Version: 1.0 Received: by 10.220.85.200 with SMTP id p8mr725575vcl.86.1235439245846; Mon, 23 Feb 2009 17:34:05 -0800 (PST) Date: Mon, 23 Feb 2009 20:34:05 -0500 Message-ID: Subject: question on HttpMessage.populateInitialHeaders From: William Tam To: camel-dev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org In HttpMessage.populateInitialHeaders(), we only propagate parameters for GET request. Does anyone see any harm in propagating other parameters of HTTP methods? //if the request method is Get, we also populate the http request parameters if (request.getMethod().equalsIgnoreCase("GET")) { names = request.getParameterNames(); while (names.hasMoreElements()) { String name = (String)names.nextElement(); Object value = request.getParameter(name); map.put(name, value); } } Thanks, William