This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreLevel up your Power BI skills this month - build one visual each week and tell better stories with data! Get started
We are running PBI Server August 2018 (15.0.2.557). We set the server properties for HTTP Headers per this post and in line with the documentation, and restarted the server.
We can see the properties being loaded in the RSPortal.log file:
2018-09-27 12:10:24.6725|INFO|1|CONFIG : AccessControlAllowOrigin = [*] (env)
2018-09-27 12:10:24.6725|INFO|1|CONFIG : AccessControlAllowHeaders = [*, X-TEST] (env)
2018-09-27 12:10:24.6725|INFO|1|CONFIG : AccessControlAllowMethods = [GET, PUT, POST, PATCH, DELETE] (env)
2018-09-27 12:10:24.6725|INFO|1|CONFIG : AccessControlExposeHeaders = [*, X-TEST] (env)
However, the headers are not returned when inspecting the HTTP calls via Chrome DevTools, Fiddler, etc.
Is this functionality now broken, or is there an additional option to configure it?
Hello,
this thread is a few months old, but we are facing the same problem. We have set the AccessControlAllowOrigin advanced property on PBI Report Server through SSMS but the server does not send the header when a request by our web app is made.
Furthermore, we can't even find the log entries OP has stated they can see on their end.
Has anyone encountered the same problem and knows a solution?
Hi everyone, do you find any solution to this issue? I am in the same situation 😞
NOTE: it is normal that the header name display without (-) ?? you know AccessControlAllowOrigin instead Access-Control-Allow-Origin ??
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |