While the patch provided (and applied long time ago) was alright, it really addresses the (albeit related)
JS2-204 issue, not this feature request.
This issue really asks for an option to use only relative urls which is very useful when using a Proxy front end like Apache.
Just by itself, this would have as side-effect that requesting secure/non-secure (Portlet) urls won't have any effect anymore.
That is a problem which
JS2-204 could (and still can) provide a solution for.
For many of my clients though, being able to dynamically switch between non-secure and secure urls really isn't that important.
Usually the whole site is put behind an already secured Apache front end.
But to be able to do so effectively, especially if the portal has to serve multiple virtual domains, the feature requested by this issue really becomes important.
I'm therefore reopening this issue and will provide a solution to set a system wide property (in jetspeed.properties) to only use relative urls: portalurl.relative.only
By default, this setting will be false, but by setting this to true, no scheme, server name and port will be used to prefix portal urls.