[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-885) Absolute paths in URL references (e.g., <a href=?>, <img src=?>, etc.) are munged. They should not be!

Absolute paths in URL references (e.g., <a href=?>, <img src=?>, etc.) are munged. They should not be! -------------------------------------------------------------------------------------------------------- Key: JBPORTAL-885 URL: http://jira.jboss.com/jira/browse/JBPORTAL-885 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal CMS Affects Versions: 2.6 Final Environment: Linux Reporter: Sandeep Pujar Assigned To: Roy Russo Priority: Minor Fix For: 2.6 Final Attachments: CMSPortlet.java BACKGROUND: CMS Portlet converts URL references in its content so those references correctly pull content into the CMS Portlet for display. The logic correctly checks to see if the url is fully qualified (e.g., starting with http://) and, if so, leaves the URL reference unchanged. The logic does not do a similar check for absolute, but unqualified, paths (e.g., starting just with /), but it should. For example, if one wants to link to a different page in the portal from within some CMS content one natural way to do it is with an absolute path. Since this doesn't work one is forced to use a full URL. But that's a problematic approach. We deploy 2 version of site, one in test and one in production. Each has a different domain so it is not appropriate to put a complete URL in our CMS content. But we definitely need our content to be able to include links to other parts of our site/portal that are not CMS content (e.g., links to other pages). The overly aggressive URL munging prevents this. FIX: The same logic needs to check whether the URL is an absolute path (starts with /) and if so, leave it unchanged as well. I.e., only relative URLs should be munged. All others should be left alone.