[jira] [Commented] (MRELEASE-908) Git HTTP authentication failing if there are spaces in the password

["gregfqt (JIRA)" <ji...@apache.org>]

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

gregfqt commented on MRELEASE-908:
----------------------------------

According to RFC 3986 (https://tools.ietf.org/html/rfc3986#section-3.2.1) username and password should be percent-encoded, so it should be "%20"

I think the cause lies in the git provider from maven-scm, see https://issues.apache.org/jira/browse/SCM-707

> Git HTTP authentication failing if there are spaces in the password
> -------------------------------------------------------------------
>
>                 Key: MRELEASE-908
>                 URL: https://issues.apache.org/jira/browse/MRELEASE-908
>             Project: Maven Release Plugin
>          Issue Type: Bug
>          Components: Git, prepare
>    Affects Versions: 2.5.1
>         Environment: Eclipse Luna in Linux with Maven 3.2.5
>            Reporter: Igor Blanco
>              Labels: authentication, regression, space, spaces
>
> I use the release plugin setting the credentials for my git repository in the settings.xml file. If I have a password without spaces it works but if it has spaces it doesn't.
> With Maven Release Plugin 2.3.2 it used to work without an issue.
> In the log of the maven execution I see that 2.3.2 used to encode the spaces in passwords as %20 but 2.5.1 does encode them as +. Not sure if this is relevant as I think both encodings are supposed to be good, but just in case.
> Thanks.



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