AEM 6.5 asset rendering issue | Community
Skip to main content
T
Tabassum
June 29, 2020
Solved

AEM 6.5 asset rendering issue

  • June 29, 2020
  • 3 replies
  • 1746 views

Hi Team,

 

We have upgraded AEM from 6.4 to 6.5. We have a set of assets (PDF) created dynamically. While dynamic creation, there is no extension added to the node. Example a pdf will be created like a node "English" and can be accessed using the node "/content/dam/project/pdf/English". Asset type is set to : application/pdf. When accessed from dam the PDFs opened in 6.4 in all browsers.

However in 6.5 with service pack the pdfs are not rendering only in chrome and bytecode, metadata is displayed in browser.
Are there any changes or configurations which need to be taken care of. Any pointers will be helpful
Thanks in advance!

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 kautuk_sahni

The solution mentioned by Tabassum:

The issue was found to be in a dependent project which had a module for updating assets. The concerned team is working on it.
It is not a AEM 6.5 issue.

 

 

3 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 29, 2020

Hi, 

Are you able to open pdf in another browser? If yes, can you  download that pfd and try to open in Chrome?

Do you have any extension that could interfere with Chrome?

Can you try in incognito mode?

Arun Patidar
    T
    TabassumAuthor
    July 6, 2020

    Thanks Tatvam, Arun for the help.
    The issue was found to be in a dependent project which had a module for updating assets. The concerned team is working on it.
    It is not a AEM 6.5 issue.

     

    Thanks,

    Tabassum

    tatvam
    tatvam
    June 29, 2020

    It is possible Chrome would be expecting some headers that is missing in 6.5 vs 6.4. You might want to scan the response headers in 6.4 vs 6.5 and find if something might be missing.

     

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity ManagerAccepted solution
      Community Manager
      July 6, 2020

      The solution mentioned by Tabassum:

      The issue was found to be in a dependent project which had a module for updating assets. The concerned team is working on it.
      It is not a AEM 6.5 issue.

       

       

      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...