[ 
https://issues.apache.org/jira/browse/CAMEL-9270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031872#comment-15031872
 ] 

ASF GitHub Bot commented on CAMEL-9270:
---------------------------------------

GitHub user koscejev opened a pull request:

    https://github.com/apache/camel/pull/702

    CAMEL-9270 trim headers before setting them via Restlet API

    As discussed in CAMEL-9270, providing a PR with CORS header trimming and 
minor related fixes.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/koscejev/camel CAMEL-9270

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/702.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #702
    
----
commit e6a8e156556c1bc698508f102aad867fe3879ed6
Author: Anton Koscejev <anton.kosce...@zoomint.com>
Date:   2015-11-30T14:27:09Z

    CAMEL-9270 trim headers before setting them via Restlet API

----


> rest-dsl - CORS support doesn't work with Restlet 2.3
> -----------------------------------------------------
>
>                 Key: CAMEL-9270
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9270
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-restlet
>    Affects Versions: 2.16.0
>            Reporter: Anton Koscejev
>            Assignee: Claus Ibsen
>             Fix For: 2.16.2, 2.17.0
>
>
> camel-restlet has upgraded to Restlet 2.3 (nice!), but this broke rest-dsl 
> CORS support, because Restlet 2.3 no longer supports setting CORS headers via 
> attributes. There are now API methods for these headers and attributes are 
> ignored with a warning.
> Example of the new API method:
> http://restlet.com/technical-resources/restlet-framework/javadocs/2.3/jse/api/org/restlet/Response.html#setAccessControlAllowOrigin%28java.lang.String%29



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to