Configuring Capability "Base URL" seems to have no effect

[matthias.sc...@materna.de]

Hello again,

we installed Nexus OSS 3.0.0-03 on box "abc.company.com" and want to add the functional hostname "nexus.company.com" as an alias before going into production.

We are used in doing such a configuration for various tools using mod_proxy so the alias is configured in the network and on the host system including apache well.

So nexus is currently available via abc.company.com AND nexus.company.com.

To force Nexus to use the new hostname I used the Capability "Base URL" and configured it using the new hostname. But although I stopped and started Nexus in the meantime it still keeps using abc.company.com e.g. for displaying links to Repositories.

Did I miss something?

Regards,
Matthias

[Peter Lynch]

First, the base URL value will only affect absolute URLs displayed in emails that are sent from Nexus.

Unfortunately though, there is a visual bug that you should be aware of where the incoming headers do not influence the URLs displayed in the UI :  https://issues.sonatype.org/browse/NEXUS-9745

Despite that bug though, accessing Nexus at nexus.company.com should work provided the correct reverse proxy settings are made.

Did I miss something?

Regards,
Matthias

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/60d8c6c6-3fe6-4a46-a699-2a21ca44007a%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.