[
https://jira.codehaus.org/browse/MRM-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354426#comment-354426
]
Alex Hinrichs commented on MRM-1863:
------------------------------------
Seems to be basically done but ;-)
- if applUrl is "http://xy"; (maybe: if protocol is the same as currently used)
the repository URL is "xy/repository/..."
- if appUrl is "https://xy"; (maybe if protocol is different from currently
used) the repository URL is "https://xy/repository/..."; (correct because fixed
by you)
- if appUrl is "joe://xy" the repository URL is "joe://xy/repository/..."
(correct because fixed by you)
- if appUrl is "file://xy" the repository URL is "file:///repository/..."
(hopefully nobody will ever use it but a strange behaviour)
- if appUrl is "file://xy/z" the repository URL is "file:///z/repository/..."
(hopefully nobody will ever use it but a strange behaviour)
In ALL cases the shown URL is correct but not the one used as link!
Don't know if this is because of your fix or another bug.
Tested on Windows 7, FF 33.0, Java 1.7.0_67
> RepositoryGroup URL is not build using the Application URL
> ----------------------------------------------------------
>
> Key: MRM-1863
> URL: https://jira.codehaus.org/browse/MRM-1863
> Project: Archiva
> Issue Type: Bug
> Components: Web Interface
> Affects Versions: 2.1.1
> Reporter: Alex Hinrichs
> Assignee: Eric Barboni
> Priority: Minor
> Attachments: repoGroupUrl.png
>
>
> The link to a Repository Group shown in the edit dialog is shown correctly
> but the underlying URL does not use the defined Application URL as prefix but
> the current URL of the browser.
> The page shown in the attached screenshot was called using a direct URL of
> "http://bgh-build-dev:8081/repo"; but the Application URL was defined as
> "https://intranet.mycomp.com/repo"; which points to our intranet proxy that is
> routing the request to the direct URL.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
