Accessing DAM images directly with publisher host in AEM 6.5

Avatar

Avatar
Level 1
bipinb15317820
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
bipinb15317820
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
bipinb15317820
Level 1

25-03-2020

Hi all,

 

In AEM 6.5 when I access a dam image on a browser it tries to download vs rendering it. Any reason why it's doing that? 

 

Steps to reproduce for we retail demo site:

1. Install AEM 6.5 as publisher

2. In any browser go to http://<publisher_host>:<publisher_port>/content/dam/we-retail/en/features/tracking.png  

 

Any thoughts? 

 

Thanks

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile
Gaurav-Behl
MVP

25-03-2020

Check the configuration under Apache Sling Content Disposition Filter or Adobe Granite REST Assets Content-Disposition Filter http://localhost:4503/system/console/configMgr

for configured patterns/extensions

 

Content-Disposition header's value inline vs attachment does that magic

 

Reference: 

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition

 

 

 

 

 

Answers (1)

Answers (1)

Avatar

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile

Avatar
Coach
Employee
jbrar
Employee

Likes

389 likes

Total Posts

869 posts

Correct reply

283 solutions
Top badges earned
Coach
Establish
Give Back 50
Give Back 5
Give Back 3
View profile
jbrar
Employee

30-03-2020

To test if this is related to content disposition,  You can try to clear the CDN cache and disable the "Enable For All Resource Paths" option at "Apache Sling Content-Disposition Filter"