The 2 first step would be to change the port to 80 and change the context path to "/" if that's your main application. It would reduce to:
If you replace the default portal
the /portal/ is there to seperate access to the portal to access to other resources like the CMS content (accessible at /content/)
That helps, thanks.
Some other observations/considerations/questions
- Replacing the default portal does not seem to be documented. I found something in http://www.jboss.com/index.html?module=bb&op=viewtopic&t=93867 which works, but I would rather not depend on the database but on the xml configuration. Can this be done?
- When I generate URL's using
createActionURLa 'auth/portal' prefix is generated even though the url from where I start is indeed http://host. Can something be done about this?
- Would there not be an advantage in trying to move away from the approach where the 'content' and 'portal' parts to navigate to either portal content or cms content. It seems that the average user (typically a viewer of content in most cases) should not be exposed to this.
I have not tried whether it actually works in Liferay, but perhaps a feature similar to Liferay's "short url" might be worth the effort (although I have no idea how easy that would be to implement)?