Skip to main content
Level 5
Jul 1, 2024 4:59 PM UTC
Solved

Asset metadata update or create folder failing in Microsoft Edge

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.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
EstebanBustamante
EstebanBustamanteAccepted solution
Adobe Champion and Community Advisor
Jul 2, 2024 1:36 PM UTC

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

Esteban Bustamante

4 replies

h_kataria
Community Advisor
Community Advisor
Jul 2, 2024 6:18 AM UTC

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 ? 

Translate
EstebanBustamante
Adobe Champion and Community Advisor
EstebanBustamanteAdobe Champion and Community AdvisorAccepted solution
Adobe Champion and Community Advisor
Jul 2, 2024 1:36 PM UTC

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

Translate
Esteban Bustamante
MukeshYadav_
Community Advisor
Community Advisor
Jul 3, 2024 12:44 PM UTC
Level 5
Jul 3, 2024 2:05 PM UTC

Hi Everyone,

The issue is resolved after clearing all time browser cache and cookies.

Thanks everyone for your valuable inputs.

Translate