Bug 793520 (JBEPP-600) - Portal names: "por", "port", "porta", "portal" caused problems with portal url links
Summary: Portal names: "por", "port", "porta", "portal" caused problems with portal ur...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-600
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: 5.1.0.ER03
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.1.0.ER04
Assignee: Thomas Heute
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-01 09:38 UTC by Michal Vanco
Modified: 2013-04-30 23:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-11 11:21:57 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-1614 0 None Closed Portal names: "por", "port", "porta", "portal" caused problems with portal url links 2012-02-16 22:17:29 UTC
Red Hat Issue Tracker JBEPP-600 0 None Resolved Portal names: "por", "port", "porta", "portal" caused problems with portal url links 2012-02-16 22:17:30 UTC

Description Michal Vanco 2010-11-01 09:38:30 UTC
project_key: JBEPP

- create portal with name: "por" or "port" or "porta" or "portal"
- go to new portal
- mouse over Site and see the links of other portals:
/classictal/public/classic/
or
/classical/public/classic/
or
/classicl/public/classic/
or
/classic/public/classic/
These links of course cause 404 error.
There is problem with url rewriting - looks like there is some String.replace or wrong regular expr.
I also verified special names like: "public","private","localhost" and worked fine.

Comment 1 Michal Vanco 2010-11-01 09:41:51 UTC
Link: Added: This issue related GTNPORTAL-1614


Comment 2 Scott Mumford 2010-11-08 07:19:47 UTC
Release Notes Docs Status: Removed: Not Required Added: Documented as Known Issue
Release Notes Text: Added: Creating new portals with names that contain all or part of the word 'portal' (such as: "por", "port", "porta" and "portal") will result in an incorrect URL writing to the Site links section of the main portal. This, in turn, will produce '404: Page not found' HTTP response errors when using these links.

Customers are advised to avoid using the problematic character sequences in new portal names until this issue is resolved.


Comment 3 Thomas Heute 2010-11-11 11:21:57 UTC
Release Notes Docs Status: Removed: Documented as Known Issue Added: Documented as Resolved Issue
Release Notes Text: Removed: Creating new portals with names that contain all or part of the word 'portal' (such as: "por", "port", "porta" and "portal") will result in an incorrect URL writing to the Site links section of the main portal. This, in turn, will produce '404: Page not found' HTTP response errors when using these links.

Customers are advised to avoid using the problematic character sequences in new portal names until this issue is resolved. Added: Creating new portals with names that contain all or part of the word 'portal' (such as: "por", "port", "porta" and "portal") resulted in an incorrect URL writing to the Site links section of the main portal. This, in turn, produced '404: Page not found' HTTP response errors when using these links.



Note You need to log in before you can comment on or make changes to this bug.