Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
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 ??
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
9 | |
5 | |
4 | |
3 | |
2 |
User | Count |
---|---|
12 | |
9 | |
7 | |
2 | |
2 |