camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11254) Default matchOnUriPrefix to false on Undertow endpoint
Date Tue, 23 May 2017 18:28:04 GMT

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

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

GitHub user onders86 opened a pull request:

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

    CAMEL-11254-Default matchOnUriPrefix to false on Undertow endpoint

    

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

    $ git pull https://github.com/onders86/camel CAMEL-11254

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

    https://github.com/apache/camel/pull/1709.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 #1709
    
----
commit 25f5ab2afb25515d77cad04366f08120dee661db
Author: onders86 <ondersezgin@gmail.com>
Date:   2017-05-23T18:26:18Z

    CAMEL-11254-Default matchOnUriPrefix to false on Undertow endpoint

----


> Default matchOnUriPrefix to false on Undertow endpoint
> ------------------------------------------------------
>
>                 Key: CAMEL-11254
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11254
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-undertow
>    Affects Versions: 2.19.0
>            Reporter: James Netherton
>            Priority: Minor
>             Fix For: 2.20.0
>
>
> Not sure why, but camel-undertow is different to the other Camel HTTP components in that
the {{matchOnUriPrefix}} endpoint property is defaulted to {{true}}.
> This makes behaviour inconsistent with other components and also makes REST DSL usage
slightly strange. I don't think we want to work with path prefixes in the context of REST
(how could you ever build a standardised API if arbitrary paths are accepted).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message