Suffix Paths Error | Community
Skip to main content
Unnikrishnankv
Level 3
October 16, 2015
Solved

Suffix Paths Error

  • October 16, 2015
  • 2 replies
  • 1195 views

    When we reference an external image in the page ( not from DAM ) and that page uses suffixes,  we see multiple calls being made to that component.

like our URL was  /content/mysite/videos.11.html/path/of/vidoefile and in the videos.html page we have a reference of image 

  <img src="images/image01.jpg" >

When this piece of  HTML code is there , we have multiple calls happening for this component  ( this multiple request happens at the server and not from the client  as we could get that available in Fiddler ) .. 

What could be the issue ? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by smacdonald2008

I am not seeing an issue with AEM code like:

<html>
<%@include file="/libs/foundation/global.jsp" %>
<cq:include script="/libs/wcm/core/components/init/init.jsp"/>
<body>
<h1>Here is where your AEM 6 interactive video component will go</h1>
 <img src="/apps/video/images/scottm.png" >   
<cq:include path="par" resourceType="foundation/components/parsys" />
</body>
</html>

There should be no issue with AEM using this code. If this behavior continues, please file a ticket. 

2 replies

smacdonald2008
Level 10
October 16, 2015

First - its best practice with AEM to place assets like images into the AEM DAM. 

You are seeing multiple calls to the component because you are referencing an image file from another location in the JCR?  I've not seen that. I am going to see if i can reduplicate that behavior. 

smacdonald2008
smacdonald2008Accepted solution
Level 10
October 16, 2015

I am not seeing an issue with AEM code like:

<html>
<%@include file="/libs/foundation/global.jsp" %>
<cq:include script="/libs/wcm/core/components/init/init.jsp"/>
<body>
<h1>Here is where your AEM 6 interactive video component will go</h1>
 <img src="/apps/video/images/scottm.png" >   
<cq:include path="par" resourceType="foundation/components/parsys" />
</body>
</html>

There should be no issue with AEM using this code. If this behavior continues, please file a ticket.