This is because Core Components are using Adaptive Image Servlet to automatically select the most appropriate rendition to display based on the size of the container in which it is displayed.
Please explore below documentation for all the details:
You should use one of below options:
sticky session: https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/dispatcher-configuration.html?lang=en#identifying-a-sticky-connection-folder-stickyconnectionsforuser synchronization: https://experienceleague.ad...
If I good understand, you want to apply some changes under /libs. If so, then this is not a proper approach, and it's against Adobe best practices.
To get rid of this issue you have few options:
follow the workaround described in SP18 release notes known issue section: https://experie...
If in your code you have Session object I would go with below code:
Why? Because you need only path to asset you would like to remove. You do not have to fetch any object, and do any other unnecessary operations. Of course using JC...
If you have link inside text component this will be a bit more difficult, you will have to:
Extract urls from text, e.g. base on a fact urls are inside href attribute of anchor html element.Create short url using resourceResolver.map method.Put back short url into your text.
Of course you will still...
If I good understand you are trying to short urls in SPA in the same way you would do that using HTL, right?
If so, then this will not work, this is one of the limitations of SPA, you can find all the limitations under https://experienceleague.adobe.com/docs/experience-manager-cloud-se...
You can use wildcard in query to achieve your goal, like this:
Please also explore official predicates documentation for more information:
AEM 6.5 - https://experienceleague.adobe.com/docs/experience-manager-65/developing/platform/query-buil...
Answering the question, why merge operation is not replacing references in cq:tags or other properties. Well according to the documentation, this is how it was designed. You can check all the details under Adobe documentation:
I would recommenced you to have a look on following Adobe documentation:
https://www.aemcomponents.dev/ - an interactive documentation, that presents sample user experience of each componenthttps://experienceleague.adobe.com/docs/experience-manager-core-components/using/wcm-components/a...