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

ASF GitHub Bot commented on SCM-846:
------------------------------------

jira-importer opened a new issue, #1071:
URL: https://github.com/apache/maven-scm/issues/1071

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 opened 
**[SCM-846](https://issues.apache.org/jira/browse/SCM-846?redirect=false)** and 
commented
   
   The fix for SCM-707 uses `URLEncoder` which does not any URL econding, but 
form encoding. `URI` with `userInfo` is the way to go according to RFC 3986.
   
   
   ---
   
   **Affects:** 1.9, 1.9.5
   
   **Issue Links:**
   - [SCM-707](https://issues.apache.org/jira/browse/SCM-707) Maven SCM should 
encode username and password in URL
    (_**"is broken by"**_)
   - [MRELEASE-908](https://issues.apache.org/jira/browse/MRELEASE-908) Git 
HTTP authentication failing if there are spaces in the password
    (_**"is depended upon by"**_)
   




> userInfo in Git HTTP URLs not escaped according to RFC 3986
> -----------------------------------------------------------
>
>                 Key: SCM-846
>                 URL: https://issues.apache.org/jira/browse/SCM-846
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.9, 1.9.5
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 1.10.0
>
>
> The fix for SCM-707 uses {{URLEncoder}} which does not any URL econding, but 
> form encoding. {{URI}} with {{userInfo}} is the way to go according to RFC 
> 3986.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to