camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Updated] (CAMEL-8625) camel-restlet - Form fields overwrite headers in InMessage
Date Thu, 09 Jul 2015 10:23:05 GMT


Claus Ibsen updated CAMEL-8625:
    Fix Version/s: Future

> camel-restlet - Form fields overwrite headers in InMessage
> ----------------------------------------------------------
>                 Key: CAMEL-8625
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-restlet
>    Affects Versions: 2.13.4, 2.14.2, 2.15.1
>         Environment: Linux
>            Reporter: Tomasz Ptak
>             Fix For: Future
> 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
> c) prefixing keys coming from the form with something, for instance "form."
> 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.
> Solution c would be rather ok as well, but I like a more, personally.
> I can provide a patch if any solution is accepted.

This message was sent by Atlassian JIRA

View raw message