[mojo-dev] [jira] (MSONAR-64) Proxy and strict reverse proxy support

[Alix Lourme (JIRA)]

Title: Message Title

Alix Lourme created an issue   Mojo's Sonar Maven Plugin / MSONAR-64 Proxy and strict reverse proxy support Issue Type: Improvement Affects Versions: 2.2 Assignee: Simon Brandhof Attachments: 201400401-2.3-SNAPSHOT-patch.txt Created: 01/Apr/14 11:41 AM Priority: Major Reporter: Alix Lourme This feature is the result of SonarQube user mailing list : Eclipse DryRun behing reverse proxy fails Hi, In the following architecture : Client (sonar-maven-plugin/EclipseDryRun/sonar-runner) <-> Proxy <-> Internet <-> Reverse Proxy (strict : with authentication challenge) <-> SonarQube Some SonarQube components fails. Mainly because HttpURLConnection doesn't implement proxy/reverse-proxy and authentication (ex : ServerMetaData). This patch in attachement is the first of three step to support this architecture for SonarQube (and could serve SONAR-2119 in the future). It replaces HttpURLConnection usage by commons HttpClient with proxy/reverse-proxy and authentication challenge support. The two other steps are sonar-runner (same process) and Eclipse plugin (give proxy configuration to sonnar-runner). Note about the patch : It is perhaps a draft, to validate/accept the demarch/approach (and before I start code pull request for sonar-runner / Eclipse plugin) ... Maven Eclipse conventions are used but not some other criterias (quality, remarks, ...) It depreciates MSONAR-42 with HttpClient:SSLContext:TrustSelfSignedStrategy. It's not tested. I need some informations about the integration test to verify this point (just install SonarQube in Https ?) Best Regards Add Comment   This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email