Asset metadata update or create folder failing in Microsoft Edge | Community
Skip to main content
S
SrikanthPo3
Level 5
July 1, 2024
Solved

Asset metadata update or create folder failing in Microsoft Edge

  • July 1, 2024
  • 3 replies
  • 1012 views

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.
Best answer by EstebanBustamante

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

3 replies

h_kataria
Community Advisor
h_katariaCommunity Advisor
Community Advisor
July 2, 2024

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 ? 

    EstebanBustamante
    Community Advisor and Adobe Champion
    EstebanBustamanteCommunity Advisor and Adobe ChampionAccepted solution
    Community Advisor and Adobe Champion
    July 2, 2024

    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
      MukeshYadav_
      Community Advisor
      MukeshYadav_Community Advisor
      Community Advisor
      July 3, 2024

      Hi,

      It seems https://author-mycompany.adobecqms.net/content/dam/mycompany/campaigns/seasonal/back-to-school/back-to-school-2024/graphic-templates/jcr:content/metadata/wfProjectURL 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:content/metadata/wfProjectURL is accessible

      Thanks

        S
        SrikanthPo3Author
        Level 5
        July 3, 2024

        Hi Everyone,

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

        Thanks everyone for your valuable inputs.

          Terms & ConditionsAccessibility statement

          Loading footer...