portals-pluto-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ate Douma <...@douma.nu>
Subject Re: [jira] Resolved: (PLUTO-82) PortalURL tied to single host specified in properties?
Date Mon, 31 Jan 2005 16:07:22 GMT
David and Jeremy,

I've been looking at this solution as I'd like to implement the same for Jetspeed-2.
And it works, but only one way.

If I request a secure PortletURL Jetspeed-2 nicely switches to a secure url.
But, if I then request a PortletURL with secure="false", I'm still running in a secure mode.
Although I indeed now am back to the non-secure (path) url again, I'm still using the
secure port which has been changed by Tomcat after I switched to secure mode.

I'm not sure what the expected behavior should be according to the specs
if I request secure="false" but this solution won't help me, using a PortletURL,
to switch back to a non-secure mode.

How to your your opinion(s) should it be made possible for the user to
switch back to non-secure mode?

Regards, Ate

David DeWolf (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/PLUTO-82?page=history ]
> David DeWolf resolved PLUTO-82:
> -------------------------------
>      Resolution: Fixed
>     Fix Version: 1.0.1-rc3
> Patch applied.  Thanks Jeremy.
>>PortalURL tied to single host specified in properties
>>         Key: PLUTO-82
>>         URL: http://issues.apache.org/jira/browse/PLUTO-82
>>     Project: Pluto
>>        Type: Improvement
>>  Components: portal driver
>>    Reporter: Jeremy Boynes
>>     Fix For: 1.0.1-rc3
>> Attachments: portalurl.patch, web.xml
>>>From the dev list:
>>Attached is a patch contribution against 1.0.1-rc1 which modifies PortalURL so that
is it not tied to the single host specified in a properties file.
>>Previously it constructed URLs based on the host.name property and the context root
of the portal. However, if the user forgot to change the name from localhost or if the server
supported multiple vhosts, then the URLs generated would be incorrect.
>>Instead, this patch maps the portal servlet twice, once with a security constraint,
once without. The implementation of PortalURL then generates the URL with the appropriate
mapping for secure or insecure mode but without specification of host, credential or port
number parts (e.g. "/pluto/portal/...")

View raw message