Thanks for the suggestion Hemant. I posed the question in more detail to Adobe Support:Our DAM has grown large and we suspect many assets are unused and could be deleted. We're using Classic UI and can select Tools, References... in the DAM Admin to see the references to individual assets, but we'd ...

How can I query to see which DAM assets in a given /content/dam path are being used most (to least) in a given /content/site path?

Hi Jorg, I did look at III and changed 2 default values (see *** 's above), along with setting a header in Apache, i.e., RequestHeader set X-Forwarded-Proto "https", specified in chapter II.  It seems to be working now.I'm not sure where the PID is referenced or how it comes into play in getting thi...

I received a hint from Adobe Support who pointed me at this article, and mentioned I look at III and IV specifically: AEM redirecting user back to http if accessed through SSL terminated Load Balancer Everything in IV was already there by default and since it was the only instruction specifically fo...

Here's some output from cURL ...the blocked mixed content in the screen.png points to http, looks like it's getting blocked before it can redirect?curl -I "http://hostname/libs/granite/core/content/login.html?resource=%2Flibs%2Fgranite%2Fcsrf%2Ftoken.json&$$login$$=%24%24login%24%24&j_reason=unknown...

It looks like those info and warn messages are in the error log on successful login as well, so they probably don't give any clues.Here's the inspect element  from Chrome on loading the SSL proxied author ...(blocked:mixed-content) (hovering over shows it is an http link). On logging in, there are t...

I have an AEM 6.3.1.2 author instance configured to authenticate either locally or with LDAP. Both authentication methods work on my local machine via localhost:4502, and when moved to the Apache host and accessed with its port number :4502 -- hostname:4502, when I access it on the Apache host via t...

Looks like the doc syntax was correct,'service httpd configtest'still gives warning :[Wed Nov 30 21:00:14.765338 2016] [core:warn] [pid 13583:tid 140210428229696] AH00111: Config variable ${PUBLISH_IP} is not definedbut 'service httpd start' works and the correct render back-end is called when ${PUB...

Unfortunately fixing the syntax only makes configtest happy, Apache still fails to start :(

FYI - I had the same issue, I set the variable within /etc/sysconfig/httpd (running centos 7 and disp 4.2.1) - it turns out the documentation showing the variable in dispatcher.any had a syntax error -${PUBLISH_IP} should be {$PUBLISH_IP}.Regards,Bill