Hi @chinmayis865517
It seems the welcome url is blocked by a rule written at line 11 in modsecurity_ams_14_r4_directory_block_logonly.conf file. Please check similar thread
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/need-to-know-more-about-this-error-on-httpd-conf/td...
Hi @PiyushBo1
Can you also try to add value property, Example
{
"component": "richtext",
"valueType": "string",
"name": "longDescr",
"value": "",
"label": "Long Description",
"description": "The description shown in Desktop and Tablet view."
}
Hi @Kamal_Kishor
For campaign the issue could not be due to PSC but the missing caching at dispatcher itself. Generally if url contains query string the dispatcher cache is skipped and PSC servlet never called instead GET request is reached at publisher.
If above assumption is correct then you need...
Hi @RahulSi13
You can add a rule for author CDN domain to override cache-control header for DAM asset
https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/cdn-configuring-traffic#response-transformations
Hi @RahulSi13
Yes, you set different cache control header in Author, you need to adjust this on dispatcher but if you are on AEMaaCS then you need to do it at CDN level.
Hi @RahulSi13
You may need to rethink caching strategy, you have no control to invalidate the user's browser cache.You can disable browser cache for those images in Author instances or serve image differently like Core Component's Adaptive Image Servlet
https://experienceleague.adobe.com/en/docs/ex...
Hi @Kamal_Kishor
We have used ACS common's Permission Sensitive Cache Servlet, you can check their logic as well.
https://adobe-consulting-services.github.io/acs-aem-commons/features/utils-and-apis/permission-sensitive-cache/index.html
Code
https://github.com/Adobe-Consulting-Services/acs-aem-co...
Hi @ZoZoZo To limit the number of components in the responsive grid, you can limit using ACS Commons's Parsys Limiter
https://adobe-consulting-services.github.io/acs-aem-commons/features/deprecated/parsys-limiter/index.html
Hi @ChrisPhillipsUC
I have not seen or heard someone using AEM for map.However, location management can be handled using Content Fragments, which support JSON exposure through GraphQL and allow for filtering and search capabilities.Maps like images is not supported in AEM.
https://experienceleague....