Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

AEM 6.5 asset rendering issue

Avatar

Level 1

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!

1 Accepted Solution

Avatar

Correct answer by
Administrator

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

View solution in original post

5 Replies

Avatar

Community Advisor

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

Avatar

Level 1

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

Avatar

Level 2

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.

 

Avatar

Correct answer by
Administrator

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