Uncaught DOMException: Blocked a frame with origin on server "https://<server_url>" | Community
Skip to main content
imrank18551706
imrank18551706
Level 2
October 30, 2018
Solved

Uncaught DOMException: Blocked a frame with origin on server "https://<server_url>"

  • October 30, 2018
  • 2 replies
  • 10038 views

Hi All,

I am facing one issue related to Uncaught DOMException: Blocked a frame with origin on server "https://<server_url>".

Uncaught DOMException: Blocked a frame with origin "https://<server_url>" from accessing a cross-origin frame.

In response header I have mentioned:

  1. X-Frame-Options: SAMEORIGIN
  2. X-Frame-Options: SAMEORIGIN

Is there any way I can resolve this issue.

Thanks in advance.

    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

    Hi,

    Adobe Experience Manager's Cross-Origin Resource Sharing (CORS) facilitates non-AEM web properties to make client-side calls to AEM, both authenticated and unauthenticated, to fetch content or directly interact with AEM. CORS configurations are managed as OSGi configuration factories in AEM, with each policy being represented as one instance of the factory.

    http://<host>:<port>/system/console/configMgr > Adobe Granite Cross Origin Resource Sharing Policy

    In this configuration, you can mention allowed origins, allowed paths, supported headers and allowed methods etc.

    Troubleshooting CORS:

    Logging is available under com.adobe.granite.cors:

    1) enable DEBUG to see details about why a CORS request was denied

    2) enable TRACE to see details about all requests going through the CORS handler

    For more information on CORS issue and troubleshooting CORS issue, please refer:

    Adobe Experience Manager Help | Understanding Cross-Origin Resource Sharing (CORS) with AEM

    I hope this information helps!

    Regards,

    Lavanya Malyala

    2 replies

    A
    Anonymous
    Accepted solution
    October 30, 2018

    Hi,

    Adobe Experience Manager's Cross-Origin Resource Sharing (CORS) facilitates non-AEM web properties to make client-side calls to AEM, both authenticated and unauthenticated, to fetch content or directly interact with AEM. CORS configurations are managed as OSGi configuration factories in AEM, with each policy being represented as one instance of the factory.

    http://<host>:<port>/system/console/configMgr > Adobe Granite Cross Origin Resource Sharing Policy

    In this configuration, you can mention allowed origins, allowed paths, supported headers and allowed methods etc.

    Troubleshooting CORS:

    Logging is available under com.adobe.granite.cors:

    1) enable DEBUG to see details about why a CORS request was denied

    2) enable TRACE to see details about all requests going through the CORS handler

    For more information on CORS issue and troubleshooting CORS issue, please refer:

    Adobe Experience Manager Help | Understanding Cross-Origin Resource Sharing (CORS) with AEM

    I hope this information helps!

    Regards,

    Lavanya Malyala

      therealsatz
      therealsatz
      Level 2
      April 12, 2020
      Were you able to resolve this issue?
      Terms & ConditionsAccessibility statement

      Loading footer...