Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332508 - Add ability to configure the URI for hosted repository and artifacts
Summary: Add ability to configure the URI for hosted repository and artifacts
Status: NEW
Alias: None
Product: Virgo
Classification: RT
Component: runtime (show other bugs)
Version: 2.1.0.RELEASE   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-14 05:24 EST by Lorie Pisicchio CLA
Modified: 2011-01-10 05:28 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lorie Pisicchio CLA 2010-12-14 05:24:47 EST 
I would like to be able to configure the URI that is used to expose hosted repository artifacts, as, in some cases, the host machine is not accessible via its hostname.

See details in the following post entry : 
http://www.eclipse.org/forums/index.php?t=msg&goto=644812&S=7f2a15d6f7092e03e5e70bdb447f7a66#msg_644812
Comment 1 heribert.hirth CLA 2010-12-14 10:47:03 EST 
This is also true for the port. The general bughere seems to be "hosted repository is not proxy aware", because if Virgo runs behind a proxy, both host name and port used for generating the artifact index URLs should be configurable. 

The port is determined in StandardRepositoryManager.determineHttpPort() by reading all Gemini connectors. But those are not proxy aware, they just return the internal connector port, too.

The ideal solution for Virgo may be to honour the relevant Tomcat proxyName and proxyPort connector settings (http://tomcat.apache.org/tomcat-5.5-doc/proxy-howto.html).