ASP.NET, New Browser Window and JavaScript Error
Hi,
I am developing an application in which I need to launch a report from BusinessObjects Enterprise (BOE). The idea is, when a user clicks the report, the BOE Web Service is called to open a session, then, the OpenDocument (proprietary functionality from BOE) is called to launch the report using the session created with the Web Service.
The issue I am having is, when the BusinessObjects Enterprise window opens, it shows the report, but the buttons to edit or export the report do not work in Firefox (only in IE). The error returned by Firefox says: "Error: Permission denied to access property 'goEdit'". As far as I have investigated, Firefox return this error because the JavaScript executed by BOE does not belong to the domain of the ASP.NET application and this is against the Same Origin Policy (or something like that).
I have tried a response.redirect and a JavaScript window.open, getting the same result from both. Is there a way to launch a completely independent page, not recognized by the browser as originated in the ASP.NET domain? (or any other idea that will make BOE's JavaScripts work even when the pages are called from ASP.NET).
Thanks in advance for your help.
Chosen solution
Hi. I was able to solve the issue, but it was using a functionality available in BusinessObjects Enterprise and not in .NET: When an OpenDocument URL is called, it has a parameter called "sWindow" with 2 possible values, "New" and "Same". If I use "Same" with a "Response.Redirect", i get the Cross-Domain issues. When I use "New", the URL is launched in a completely new window and there is no cross-domain issue.
Thanks for all your help and support.
Read this answer in context 👍 0All Replies (5)
Try the add-on User Agent Switcher to make the page think you're on Linux or another platform.
Some pages return an error when they don't recognize the useragent string.
Also, it may be a cross-site scripting issue preventing page update.
Please return and report your progress.
Modified by sctl
Thanks for the help.
The issue is with Firefox in Windows (I have tested Firefox from 4 to 8) under Windows XP, 7, 2003 and 2008; all with the same result. I suppose the issue is due to Cross-Site restrictions.
In this particular case, I am not concerned about the security issues of cross-site as we are working with applications in an Intranet.
Can you make use of HTML5's serializing html fragments with cross document messaging?
Never used it, but I can give it a try. Any idea is worth a try. Thanks.
Chosen Solution
Hi. I was able to solve the issue, but it was using a functionality available in BusinessObjects Enterprise and not in .NET: When an OpenDocument URL is called, it has a parameter called "sWindow" with 2 possible values, "New" and "Same". If I use "Same" with a "Response.Redirect", i get the Cross-Domain issues. When I use "New", the URL is launched in a completely new window and there is no cross-domain issue.
Thanks for all your help and support.