-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 6.0.6 GA, 6.1.0 CE GA1, 6.2.0 CE M2
-
Fix Version/s: 6.0.X EE, 6.1.1 CE GA2, 6.1.20 EE GA2, 6.2.0 CE M2
-
Component/s: Site Templates
-
Labels:
-
Environment:Mac or Windows deployment using Tomcat 6.0.29 and Java 1.6
-
Branch Version/s:6.1.x, 6.0.x
-
Backported to Branch:Committed
-
Epic/Theme:
-
Fix Priority:4
-
Git Pull Request:
If the cdn.host.http or cdn.host.https properties are defined in portal-ext.properties, the host is incorporated into the URL for loading css.jsp within top_head.jsp. Line 30 shows the following, which includes a call to getCDNHost():
<link href="<%= HtmlUtil.escape(PortalUtil.getStaticResourceURL(request, themeDisplay.getCDNHost() + themeDisplay.getPathContext() + "/html/portal/css.jsp")) %>" rel="stylesheet" type="text/css" />
This is not correct. There is no sense in putting a JSP file on the CDN, as it won't be processed. The logic should be updated to remove the call to getCDNHost() and just reference the file from the Liferay server.
I have seen older tickets reported that are related to this (see LPS-12383), but it looks like these issues are only being addressed on a case-by-case basis. Given that this looks like the fourth or fifth such issue, would it make sense to do a deeper scan on all logic related to CDN usage, so we are sure that JSPs and other dynamic files aren't expected to be on the CDN?