[CONTINUUM-2331] adding projects pom.xml from https-Url through PROXY does not work (proxy overridden)

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.2.3
• Component/s: Core system
• Labels: backlog-to-cleanup
• Environment: regardless: tested on windows XP sp3 and ubuntu linux 8.10
• Assignee: Unassigned
• Reporter: Felix Herzog
• Created: 13/Aug/09 10:03
• Updated: 20/Nov/12 01:09

Description

Our svn is only reachabble by https. so to get a pom by URL (maven 2 project) you have tio use https.
But we are behind a proxy and there is a need to use that proxy.
The connection fails with following error:

1381951 [addMavenTwoProjectBackgroundThread] INFO org.apache.http.impl.client.DefaultRequestDirector - I/O exception (javax.net.ssl.SSLException) caught when processing request: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
1381951 [addMavenTwoProjectBackgroundThread] INFO org.apache.http.impl.client.DefaultRequestDirector - Retrying request
1381951 [addMavenTwoProjectBackgroundThread] INFO org.apache.http.impl.client.DefaultRequestDirector - I/O exception (javax.net.ssl.SSLException) caught when processing request: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
1381951 [addMavenTwoProjectBackgroundThread] INFO org.apache.http.impl.client.DefaultRequestDirector - Retrying request
1381967 [addMavenTwoProjectBackgroundThread] INFO org.apache.http.impl.client.DefaultRequestDirector - I/O exception (javax.net.ssl.SSLException) caught when processing request: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake

We added the .crt to our Java environment, we added it to the .subversion folder of the previlegued continuum user (linux)... but always the same. So we sniffed the traffic and found out:
The connection/the handshake does NOT happen through the Proxy. It seems continuum tries a direct connection and thus: fails.

if we do a workaround:
check out the files (including the poms), set up a local apache pointing to the checked out files. add the project... then you feel free ALSO using the svn (provided by https) through the proxy. Its only at the initioal addition of the projeect.

Seems the https-functionality for adding projects ignores proxy-settings.

thanks.