[jira] [Commented] (CAMEL-10334) Use of whitespaces in remotePath

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user undso opened a pull request:

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

    CAMEL-10334 Use of whitespaces in remotePath

    https://issues.apache.org/jira/browse/CAMEL-10334

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

    $ git pull https://github.com/undso/camel master

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

    https://github.com/apache/camel/pull/1184.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 #1184
    
----
commit aa9d508bd3d21f0ff914f08b5772a2507f2e220e
Author: Alexander Friedrichs <un...@users.noreply.github.com>
Date:   2016-09-21T06:03:12Z

    Handle whitespaces in remotePath

----


> Use of whitespaces in remotePath
> --------------------------------
>
>                 Key: CAMEL-10334
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10334
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.17.3
>            Reporter: Alexander Friedrichs
>            Priority: Minor
>              Labels: camel, dropbox
>
> With DropBox it is possible to use filepaths and filenames with whitespaces in it. The attribute remotePath can't support this yet.
> Camel translate a remotePath like this:
> {{to("dropbox://search?accessToken=<accessToken>&clientIdentifier=<clientIdentifier>&remotePath=/path+with+spaces")}}
> to {{/path with spaces}} and this hits the DropboxConfigurationValidator.
> One possible solution, replace whitespaces with plus.
> I created a patch with a unit test and will make a pull request for this.



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