Must-share information (formatted with Markdown):
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
Hey there.
Thanks for including a screenshot. The error in the upper right (This request cannot be processed) likely masks the real error.
Do you see any more info in the logs (specifically web.log)?
Hi, thanks for responding. There are no errors in any of the logs. I did another test to confirm this and still nothing in the logs.
Which is odd because when I hit F12 to view the browser debug console I see the below error message:
If your SonarQube Server is being served over HTTPS, it might be that the web request is never making it to the SonarQube server (you can look for this exact URL in your access.log file), in which case you’ll need to find out what’s blocking it at the proxy/load-balancer level.
Try clicking on the URL in this screenshot (/api/measures/component....). What error message do you get? Do you see the request in your access.log file?
There were no entries in access.log for that specific URI, despite repeated 404s in the browser. When I truncated the URI to reduce the length of the request I got a 200 response and a load of JSON.
So it looks as if something on the network or server is just blocking the request, before it gets to Sonar, or possibly (less likely I suppose), Tomcat doesn’t like the length of the request. The full failing request (minus the exact hostname) is below:
[https://xxxxxxxxxxx.xxxxxx.cloudapp.azure.com/api/measures/component?additionalFields=period%2Cmetrics&component=Cornwall_Council_Website_DotNet_Core_Cornwall_Council_Website_DotNet_Core_AZOS8_RrVsidYgzPYnLm&metricKeys=accepted_issues%2Cnew_software_quality_maintainability_remediation_effort%2Cnew_technical_debt%2Chigh_impact_accepted_issues%2Cblocker_violations%2Csoftware_quality_blocker_issues%2Cbugs%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%2Ccomplexity%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%2Ceffort_to_reach_software_quality_maintainability_rating_a%2Cfalse_positive_issues%2Cfiles%2Cfunctions%2Cgenerated_lines%2Cgenerated_ncloc%2Csoftware_quality_high_issues%2Cinfo_violations%2Csoftware_quality_info_issues%2Cviolations%2Cprioritized_rule_issues%2Cline_coverage%2Cnew_line_coverage%2Clines%2Cncloc%2Clines_to_cover%2Cnew_lines_to_cover%2Csoftware_quality_low_issues%2Csoftware_quality_maintainability_issues%2Csoftware_quality_maintainability_rating%2Csqale_rating%2Cnew_maintainability_rating%2Cnew_software_quality_maintainability_rating%2Cmajor_violations%2Csoftware_quality_medium_issues%2Cminor_violations%2Cnew_accepted_issues%2Cnew_blocker_violations%2Cnew_software_quality_blocker_issues%2Cnew_bugs%2Cnew_code_smells%2Cnew_critical_violations%2Cnew_software_quality_high_issues%2Cnew_info_violations%2Cnew_software_quality_info_issues%2Cnew_violations%2Cnew_lines%2Cnew_software_quality_low_issues%2Cnew_software_quality_maintainability_issues%2Cnew_major_violations%2Cnew_software_quality_medium_issues%2Cnew_minor_violations%2Cnew_software_quality_reliability_issues%2Cnew_security_hotspots%2Cnew_software_quality_security_issues%2Cnew_vulnerabilities%2Copen_issues%2Cprojects%2Calert_status%2Creleasability_rating%2Csoftware_quality_reliability_issues%2Csoftware_quality_reliability_rating%2Creliability_rating%2Cnew_reliability_rating%2Cnew_software_quality_reliability_rating%2Csoftware_quality_reliability_remediation_effort%2Creliability_remediation_effort%2Cnew_reliability_remediation_effort%2Cnew_software_quality_reliability_remediation_effort%2Creopened_issues%2Csecurity_hotspots%2Csecurity_hotspots_reviewed%2Cnew_security_hotspots_reviewed%2Csoftware_quality_security_issues%2Csecurity_rating%2Csoftware_quality_security_rating%2Cnew_software_quality_security_rating%2Cnew_security_rating%2Csoftware_quality_security_remediation_effort%2Csecurity_remediation_effort%2Cnew_security_remediation_effort%2Cnew_software_quality_security_remediation_effort%2Csecurity_review_rating%2Cnew_security_review_rating%2Cskipped_tests%2Cstatements%2Csqale_index%2Csoftware_quality_maintainability_remediation_effort%2Csoftware_quality_maintainability_debt_ratio%2Csqale_debt_ratio%2Cnew_sqale_debt_ratio%2Cnew_software_quality_maintainability_debt_ratio%2Cuncovered_conditions%2Cnew_uncovered_conditions%2Cuncovered_lines%2Cnew_uncovered_lines%2Ctest_execution_time%2Ctest_errors%2Ctest_failures%2Ctest_success_density%2Ctests%2Cvulnerabilities]
Ok, so after a bit more digging it turns out our server is setup on Windows Server with a URL Rewrite via IIS.
IIS defaults limit the Querystring length to 2048. That needed to be increased.
You can do that in Request Filtering in IIS:
then:
then:
Thanks for the follow-up! For what it’s worth, this is documented here.
