Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

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

Avatar

Level 2

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.

cross_origin_error.png

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.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

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

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

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

Avatar

Level 2
Were you able to resolve this issue?
The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----