CORS issue postMessage target origin does not match

Question

I have a web application currently in development built in JavaScript ES6 modules using webpack (in VS Code)

I am getting... Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://localhost:4015') does not match the recipient window's origin ('http://localhost:4010').

I have the report server as 4015 and the lite-server of dev mode is running at 4010

I have connected SQ management Studio to ReportServer and set AccessControlAllowOrigin to each of http://localhost:4010, http://localhost:4015, http://localhost and *, restarted the service but the error persists.

The web application embeds an iframe element with the src attribute set to the url of the report. The report is rendered bu I interpret this as meaning the report has tried to fire some notification messages (loaded, perhaps) and failed with this message.

Any ideas or help would be appreciated as I have exhausted the internet searching for a solution!

d_gosbell · Answer

ajelcocks&nbsp;wrote:
The web application embeds an iframe element with the src attribute set to the url of the report. The report is rendered bu I interpret this as meaning the report has tried to fire some notification messages (loaded, perhaps) and failed with this message.
&nbsp;
Any ideas or help would be appreciated as I have exhausted the internet searching for a solution!

Have you included the rs:embed=true query string parameter in the report url? If you have not included the rs:embed parameter PBIRS will try to render all the navigation elements around the report which might be what is causing this issue.

ajelcocks · Answer

Yes, I have. This is the url and hostdata&nbsp;&nbsp;&nbsp;let&nbsp;hostdata&nbsp;=&nbsp;{&nbsp;&nbsp;&nbsp;&nbsp;Build:&nbsp;"15.0.1102.620",&nbsp;&nbsp;&nbsp;&nbsp;ExternalUser:&nbsp;"True",&nbsp;&nbsp;&nbsp;&nbsp;IsPublicBuild:&nbsp;true,&nbsp;&nbsp;&nbsp;&nbsp;Host:&nbsp;"Microsoft.ReportingServices.Portal.Services",&nbsp;&nbsp;&nbsp;&nbsp;HashedUserId:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"A4A5A6E6E5E4F5027C9EE13957705E6E3112D06DDF95F57FBB4A161",&nbsp;&nbsp;&nbsp;&nbsp;InstallationId:&nbsp;"abcde-9700-4abc-abcd-a1234abcd1234",&nbsp;&nbsp;&nbsp;&nbsp;IsEnabled:&nbsp;true,&nbsp;&nbsp;&nbsp;&nbsp;Edition:&nbsp;"PBIRS&nbsp;Developer",&nbsp;&nbsp;&nbsp;&nbsp;AuthenticationTypes:&nbsp;"RSWindowsNTLM",&nbsp;&nbsp;&nbsp;&nbsp;NumberOfProcessors:&nbsp;1,&nbsp;&nbsp;&nbsp;&nbsp;NumberOfCores:&nbsp;4,&nbsp;&nbsp;&nbsp;&nbsp;IsVirtualMachine:&nbsp;false,&nbsp;&nbsp;&nbsp;&nbsp;MachineId:&nbsp;"01020304B1B2B3B41234567890ABCCBE",&nbsp;&nbsp;&nbsp;&nbsp;CountInstances:&nbsp;1,&nbsp;&nbsp;&nbsp;&nbsp;Count14xInstances:&nbsp;0,&nbsp;&nbsp;&nbsp;&nbsp;Count13xInstances:&nbsp;0,&nbsp;&nbsp;&nbsp;&nbsp;Count12xInstances:&nbsp;0,&nbsp;&nbsp;&nbsp;&nbsp;Count11xInstances:&nbsp;0,&nbsp;&nbsp;&nbsp;&nbsp;ProductSku:&nbsp;"SSRSPBI"&nbsp;&nbsp;};&nbsp;&nbsp;let&nbsp;reportUrl&nbsp;=&nbsp;`http://localhost:4015/powerbi/?rs:embed=true&amp;id=12345678-abcd-1234-abcd-ee77dd66&amp;formatLocale=en-US&amp;hostdata=${JSON.stringify(&nbsp;&nbsp;&nbsp;&nbsp;hostdata&nbsp;&nbsp;)}`;

d_gosbell · Answer

Sorry, that was the only idea I had.
&nbsp;
I'm not familiar with the hostdata parameter. I have not seen it used before with PBIRS and can't see any documentation on it. But it does not look like any of the information you are passing there would influence CORS in any way.
&nbsp;
Are you able to see the call stack of that exception using the chrome dev tools? That my give you a hint as to whether it's your app or the report triggering this.

ajelcocks · Answer

I got the hostdata parameter from one of the examples on the web. I don't know if it does anything but the example used it so I left it in.&nbsp;If I change 4015 in the url of the report server to 4010 and use fidler to redirect to 4015 then the error does not occur. This suggests to me it is the report server. The error itself would support that, indicating that postMessage was invoked by code delivered from 4015 for a recipient at 4010&nbsp;Thanks for the suggestions.&nbsp;For anyone else reading this - the 'solution' I found is to use fiddler and add a rule to redirectI changed the port of the url for the powerbi report in my we app from 4015 (the powerbi port) to 4010 (my apps port) and added a rule in fiddler to intercept that and change the port to 4015. This 'spoofs' the report server and so the error does not occur.&nbsp;Maybe not the 'real' solution, but it works.

Forum Discussion

CORS issue postMessage target origin does not match

4 Replies

Related content

Targets/Goals best practice

gps.js error - gps.js:114 Failed to execute 'postMessage' on 'DOMWindow': The target origin provided

Publishing into Target Warehouse using VS Code causing issues

Original table name

Calculating Days late with specific target times