A lot of projects with long project keys result in an empty overview page

SonarQube
1

Since we have created few projects (around 50) with to long project keys, SonarQube doesn’t show any project in home page. In browsers network tab we found also HTTP 500 error.
Also used the same URI in API call request return the same error. Can we somewhere change max URI length to handle this long request.

To reproduce the issue you can run the script below and visit the SQ start/home page

#!/bin/bash

for (( c=1; c<=45; c++ ))

do

echo $c

NEW_UUID=$(cat /dev/urandom | tr -dc ‘a-zA-Z0-9’ | fold -w 32 | head -n 1)

echo $NEW_UUID

curl -v -X POST -u ac4a46556a5ad237860daafbf7c2a19ee8ffe5bd "http://sonarqube-core:9000/sonarqube/api/projects/create?name=$NEW_UUID&project=$NEW_UUID.$NEW_UUID.$NEW_UUID.$NEW_UUID:$NEW_UUID.$NEW_UUID"

done

2

Hi,

Could you explain why you have such long project names?

 
Ann

3

Hello,

this issue has been reported to me by one of our projects - I sadly do not know the exact reason why their project keys became that long, but they mentioned it was working at the beginning. It might not be a best practice to have project keys that are sooo long, but anyway I guess SQ should either reject those long project keys or - If they are accepted - Always show them on the start page.

I guess the issue itself is related to the length of the URL - Is there an option to define the maximum length of an URL like https://httpd.apache.org/docs/trunk/mod/core.html#limitrequestline for Apache?

Marvin

5

Hi,

You said in your first message that they are some error 500, could you please return the errors you’ll find in web.log ?

Regards,
Julien Lancelot

6

Hello @julienlancelot (and a happy new year),

the 500 return code was found while having a look at the network tab of the development tools from Chrome. We checked the log-files of the server, but couldn’t find a meesage related to it. In which log file would you expect the error?

Thank you and best regards,

Marvin

7

Hi @Marvin123 and happy new year to you !

You need to check in {SONARQUBE}/logs/web.log.

Regards,
Julien Lancelot

8

Hm, that log sadly did not contain an error :frowning: Could it be related to the log-level?