Was able to get the redirects to work for both content URLs and teaser image URLs. Below are few rules from my local instance { "jcr:primaryType": "sling:Folder", "jcr:createdBy": "admin", "hidden": "true", "jcr:created": "Tue Sep 17 2019 15:26:49 GMT-0700", "http": { "jcr:primaryType"...

Rajeev, did you get to closure on this scenario? If yes, please share the same with us.

This one's a tricky requirement, I believe this can be achieved via custom predicate [0] where the sorting has to happen based on the number of occurrences(count) of a search term. Here's a another forum [1] somewhat similar but with pages where the requirement was search for occurrence of a search ...

I feel this is expected because the request is for an asset directly which returns binary. Try requesting for a path(/content/dam/barn-dnb-no/page-images/article-pages) which should return the expected response headers related to cache. Post this the actual test you should be doing is if the cache i...

Please check if the path in question(/content/dam/barn-dnb-no/page-images/article-pages/illustration_barne hagefradrag.svg) is cached on the dispatcher. if not try to cache the files for TTL to work.

You could use Rsync for about 2 times while the system is running and then the last rsync can be taken by shutting down the server where the downtime would be less as the last rsync would only copy delta and most of the data is already copied from previous rsync.Rsync for the 1st time while the inst...

Below are few pointers I could think of to further debug the problem.1. What is the behaviour when the URL is accessed directly via publish ip? Thread dumps might give a better idea as to what's happening. Capture thread with top command output so you can identify the thread consuming CPU. [0] gives...

StartupMode is RESTART from upgrade logs, it should be UPGRADE when you unpack the jar. make sure all pre upgrade tasks are completed and quickstart.properties file is generated as mentioned in [0][0]Pre-Upgrade Maintenance Tasks

Seems to be an issue with 6.5.1 and 6.5.2 which should be fixed in 6.5.3 scheduled to be released in December this year. Until then replace line 251 at /libs/dam/gui/coral/components/admin/moveassetwizard/clientlibs/js/wizard.js with the below code. you could create an overlay for the same and later...

Might be a case duplicate requests to Coral JS and CSS files. Eliminating the source of these duplicate request should resolve the noted error