Hi All,
Our content authors are facing issues while updating asset metadata and click of Save/Submit button or even while creating a folder in Edge browser while the same actions on Chrome are working fine. User permissions does not seem to be an issue as the users are able to perform same activities in Chrome. Browser console has below error messages
Attached screenshots of error on save/submit.
Anyone faced similar issues, can you please help us with resolution. We are on AEM 6.5.17.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi,
The issue is caused because you are trying to access a non-secure resource (a script via http) from a secure resource (a page in https). Can you check if in Chrome you are also requesting the same non-secure resources (http://author-mycompany65prd.adobecqms.net/error.html')? If you are seeing that in Chrome this is HTTPS then most likely it is browser cache issue and flushing it should fix it.
Hope this helps
This is rather strange. Can you try comparing as well as share request/response headers for the POST request when you try to create a new folder in Chrome v/s Edge ?
Hi,
The issue is caused because you are trying to access a non-secure resource (a script via http) from a secure resource (a page in https). Can you check if in Chrome you are also requesting the same non-secure resources (http://author-mycompany65prd.adobecqms.net/error.html')? If you are seeing that in Chrome this is HTTPS then most likely it is browser cache issue and flushing it should fix it.
Hope this helps
Hi,
It seems https://author-mycompany.adobecqms.net/content/dam/mycompany/campaigns/seasonal/back-to-school/back-... is cached in Chrome so it doesn't try to load http://author-mycompany65prd.adobecqms.net/error.html
In edge back-to-school is not accessible so it redirect to error which is not https.
Try to check if /content/dam/mycompany/campaigns/seasonal/back-to-school/back-to-school-2024/graphic-templates/jcr:c... is accessible
Thanks
Hi Everyone,
The issue is resolved after clearing all time browser cache and cookies.
Thanks everyone for your valuable inputs.
Views
Likes
Replies
Views
Likes
Replies