[SonarQube 5.1.2] Unable to use a context root

[Sébastien Piller]

Hi,

With SonarQube 5.1.2, I can not set a context root different from the default (property sonar.web.context), because that lead to issues with the filters (when I browse for example http://mysonar/sonar/issues/search#id=5, I get 404 Not Found in the console to http://mysonar/api/issue_filters/show/2 - notice the absence of the context root).

Reverting to the default (empty value in sonar.web.context) fixes the issue.

Is it already known?

[Sébastien Piller]

I mean, the 404 obviously try to get to http://mysonar/api/issue_filters/show/5, not /show/2

[Fabrice Bellingard]

I know it's not the answer you're expecting, but I just wanted to warn you that the ability to set a webapp context is dropped in SonarQube starting with upcoming 5.4 (https://jira.sonarsource.com/browse/SONAR-7122). This was causing too much side effects and bugs for very little added value.

Best regards,

Fabrice BELLINGARD | SonarSource SonarQube Platform Product Manager http://sonarsource.com

On Thu, Feb 11, 2016 at 5:14 PM, <shield...@gmail.com> wrote:

I'm having issues too w/ the context.  Specifically, I just added installed the LDAP filter and when the plugin constructs URL's to redirect, it's generating URL's w/o the context root....

--
You received this message because you are subscribed to the Google Groups "SonarQube" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarqube+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarqube/8ff65977-c48d-4754-a154-70d56c2d8448%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jared Shields]

Ah. No worries. I gave up and adjusted our reverse proxy to instead rely on the hostname rather than the url path. Good to know though, thanks!

Sent from Outlook Mobile