[ 
http://jira.codehaus.org/browse/WAGONHTTP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Brett Porter closed WAGONHTTP-16.
---------------------------------

         Assignee: Brett Porter
       Resolution: Fixed
    Fix Version/s: 1.0-beta-3

applied, thanks

> when repository URL contians a trailing slash, resolved URLs contain 
> duplicate slashes
> --------------------------------------------------------------------------------------
>
>                 Key: WAGONHTTP-16
>                 URL: http://jira.codehaus.org/browse/WAGONHTTP-16
>             Project: wagon-http
>          Issue Type: Bug
>    Affects Versions: 1.0-beta-2
>            Reporter: Nathan Beyer (Apache)
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.0-beta-3
>
>         Attachments: http-trailing-slash-patch.diff
>
>
> When a repository URL is configured with a trailing slash, such as 
> http://repo1.maven.org/maven2/, the URLs that are constructed contain double 
> slashes. The currently assembled URL is something like 
> http://repo1.maven.org/maven2//org/apache/maven/maven-2.0-20050406.034330-1.pom.
> As a URL that ends in a directory should end with a slash, per the URI 
> syntax, the use of trailing slashes in configured URLs should be a common 
> occurrence. This generally doesn't affect most web servers, as most operating 
> systems don't allow directories with an empty string name, which is what a 
> "//" would indicate.
> I've attached a simple patch that cleans this up for wagon-http and 
> wagon-http-lightweight. The patch includes two new test cases to exercise 
> this code. The knew test cases are just duplicates of existing test cases, 
> but with a fixture repository URL that ends in a slash.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to