Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 43DCA174F9 for ; Mon, 13 Apr 2015 14:36:28 +0000 (UTC) Received: (qmail 93506 invoked by uid 500); 13 Apr 2015 14:36:12 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 93466 invoked by uid 500); 13 Apr 2015 14:36:12 -0000 Mailing-List: contact issues-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 issues@camel.apache.org Received: (qmail 93457 invoked by uid 99); 13 Apr 2015 14:36:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Apr 2015 14:36:12 +0000 Date: Mon, 13 Apr 2015 14:36:12 +0000 (UTC) From: "Tomasz Ptak (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-8625) Form fields overwrite headers in InMessage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tomasz Ptak created CAMEL-8625: ---------------------------------- Summary: Form fields overwrite headers in InMessage Key: CAMEL-8625 URL: https://issues.apache.org/jira/browse/CAMEL-8625 Project: Camel Issue Type: Bug Components: camel-restlet Affects Versions: 2.15.1, 2.14.2, 2.13.4 Environment: Linux Reporter: Tomasz Ptak DefaultRestletBinding adds values from submitted form as headers in the inMessage of the exchange. As a result it is close to impossible to rely on any of the values provided. Suggested solution: a) form values should be stored separately, or b) populating headers from the form should fail if a header with this key already exists Solution a is a safer solution which will break compatibility with previous versions of Apache Camel (it can also be spread over a number of releases, first introducing new field for form values and logging a warning if form data is being extracted, next making it configurable and disabled by default, then removing this functionality). Solution b is backwards compatible if this behaviour is not used as a feature (if it is, it should not). That said someone could still use it to populate RestletRequest-like headers in the Message. I can provide a patch if any solution is accepted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)