brunp wrote:
Here is the thing, with ProxyName and ProxyPort defined in the
server.xml
file for Tomcat, the login
works and redirects me to the login page as if I were to login
using the
proxyname instead.
The login works without a problem at that point because the FQDN is
defined in my hosts file and on
the DNS server.
However, if I remove ProxyName and ProxyPort, then the only page
visible
is my login page, but the
minute I hit login and issue the redirect call within my
LoginProxyServlet
class, all goes to hell.....so
it has something to do with the redirect rules.
Paul
On another note, and it is likely realted, nobody has yet been able to
provide details on the following Jetspeed parameter:
portalurl.relative.only
I had originally assumed that upgrading to Jetspeed 2.1.3 would
allow me to
get away from using DNS names and get me into using IP addresses.
However, I have yet to determine if this parameter has an effect or
not.
Could anyone let me know how I can test this out?
Try changing this parameter by setting it to true in
jetspeed.properties, restart server and look at the URLs generated ,
they will now be relative
portalurl.relative.only=true
This setting as true will generate all Portal URLs without schema,
servername or port. Defining this to true (default = false) means
requesting secure Portlet URLs won't have any effect anymore. But a
proxy frontend (like Apache) can still be used for securing the whole
site.
See:
https://issues.apache.org/jira/browse/JS2-275
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
