Measures not shown when using https url

SonarQube Server / Community Build
1

Hello,

We have a SonarQube instance version 8.2.0. The URL is something like this: http://ourhost:9000/SonarQubeEnterprise.

To make the pull request decorations work we configured a reverse proxy and set the setting
sonar.core.serverBaseURL to be https://ourhost:9010/SonarQubeEnterprise.

Our problem is that when accessing the SonarQube instance by the HTTPS URL the tab Measures in projects doesn’t show anything and an error appears saying “The request cannot be processed. Try again later.”. When accessing the same project via HTTP URL the measurements are displayed correctly.

We tried to see what it happens in the console and it seems that is trying to do a request that has a very long URL: https://ourhost:9010/SonarQubeEnterprise/api/measures/component?additionalFields=periods&component=ourproject&metricKeys=new_technical_debt%2Cblocker_violations%2Cbugs%2Cburned_budget%2Cbusiness_value%2Cclasses%2Ccode_smells%2Ccognitive_complexity%2Ccomment_lines%2Ccomment_lines_density%2Cbranch_coverage%2Cnew_branch_coverage%2Cconditions_to_cover%2Cnew_conditions_to_cover%2Cconfirmed_issues%2Ccoverage%2Cnew_coverage%2Ccritical_violations%2Ccritical_severity_vulns%2Ccomplexity%2Cdirectories%2Cduplicated_blocks%2Cnew_duplicated_blocks%2Cduplicated_files%2Cduplicated_lines%2Cduplicated_lines_density%2Cnew_duplicated_lines_density%2Cnew_duplicated_lines%2Ceffort_to_reach_maintainability_rating_a%2Cfalse_positive_issues%2Cfiles%2Cfunctions%2Cgenerated_lines%2Cgenerated_ncloc%2Chigh_severity_vulns%2Cinfo_violations%2Cinherited_risk_score%2Cviolations%2Cline_coverage%2Cnew_line_coverage%2Clines%2Cncloc%2Clines_to_cover%2Cnew_lines_to_cover%2Clow_severity_vulns%2Csqale_rating%2Cnew_maintainability_rating%2Cmajor_violations%2Cmedium_severity_vulns%2Cminor_violations%2Cnew_blocker_violations%2Cnew_bugs%2Cnew_code_smells%2Cnew_critical_violations%2Cnew_info_violations%2Cnew_violations%2Cnew_lines%2Cnew_major_violations%2Cnew_minor_violations%2Cnew_security_hotspots%2Cnew_vulnerabilities%2Copen_issues%2Cprojects%2Calert_status%2Creleasability_rating%2Creliability_rating%2Cnew_reliability_rating%2Creliability_remediation_effort%2Cnew_reliability_remediation_effort%2Creopened_issues%2Csecurity_hotspots%2Csecurity_hotspots_reviewed%2Cnew_security_hotspots_reviewed%2Csecurity_rating%2Cnew_security_rating%2Csecurity_remediation_effort%2Cnew_security_remediation_effort%2Csecurity_review_rating%2Cnew_security_review_rating%2Cskipped_tests%2Cstatements%2Cteam_size%2Csqale_index%2Csqale_debt_ratio%2Cnew_sqale_debt_ratio%2Ctotal_dependencies%2Ctotal_vulnerabilities%2Cuncovered_conditions%2Cnew_uncovered_conditions%2Cuncovered_lines%2Cnew_uncovered_lines%2Ctest_execution_time%2Ctest_errors%2Ctest_failures%2Ctest_success_density%2Ctests%2Cvulnerabilities%2Cvulnerable_component_ratio%2Cvulnerable_dependencies%2Cwont_fix_issues

Do you know how we could overcome this issue?

1 Like
2

Hi,

I guess you’re using an IIS proxy? I think by default it has a lower URL length than most but I believe it’s tunable.

 
HTH,
Ann

3

Hi,

Thank you for the suggestion. I’ve increased the URL max length of the reverse ISS proxy and it works now.

1 Like
4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.