We have a seiries of reports which are loaded into an I-Frame. The address the I-frame points to is not the same domain as the website which contains the I-Frame, but the server which host the "report" url is located on another domain. On our testing servers we seemed to have had no problem with this configuration, but when we posted this solution into production we ran across a problem with Internet Explorer.
In FireFox browsers, the reports load up correctly and the process is transparent to the end user and they have no idea the reports are in fact a separate url. But when attempting to load the reports in IE, the report viewer loads up, but it contains an error message to the effect of "Report is unavailable, or session has expired". If we add the 'report' url as a trusted site we can get the reports to load correctly in IE. Since we have several thousand users, most of which are not technically savy, having each one add the url as a trusted site would not be a practical solution.
For the time being, we have the reports 'popping up' in a new window and they seem to load up fine. We are hoping this is a temporary solution since we are trying to avoid popups and all the problems associated with popups(such as popup blockers). I know hosting the reports on a separate domain is not an ideal situation, but it is the one I am presented with, and for the time being it is what I am required to work with. I was hoping someone could point me in the right direction and as to where I could begin to look for the reason the I-frame will not correctly load the 'report' URL when browsing with IE.
An additonal note, both sites use a SSL certificate, but removing the certificates seems to make no difference.
Thanks in advance
In FireFox browsers, the reports load up correctly and the process is transparent to the end user and they have no idea the reports are in fact a separate url. But when attempting to load the reports in IE, the report viewer loads up, but it contains an error message to the effect of "Report is unavailable, or session has expired". If we add the 'report' url as a trusted site we can get the reports to load correctly in IE. Since we have several thousand users, most of which are not technically savy, having each one add the url as a trusted site would not be a practical solution.
For the time being, we have the reports 'popping up' in a new window and they seem to load up fine. We are hoping this is a temporary solution since we are trying to avoid popups and all the problems associated with popups(such as popup blockers). I know hosting the reports on a separate domain is not an ideal situation, but it is the one I am presented with, and for the time being it is what I am required to work with. I was hoping someone could point me in the right direction and as to where I could begin to look for the reason the I-frame will not correctly load the 'report' URL when browsing with IE.
An additonal note, both sites use a SSL certificate, but removing the certificates seems to make no difference.
Thanks in advance
1 Answer, 1 is accepted
0
Hello Gene,
I think there is a way to work around the problem. If you configure the Session state for the report's web application not to use cookies you may get it working. Just add the following line in the web.config file:
<sessionState cookieless="true"></sessionState>
Hope this helps.
Greetings,
Chavdar
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I think there is a way to work around the problem. If you configure the Session state for the report's web application not to use cookies you may get it working. Just add the following line in the web.config file:
<sessionState cookieless="true"></sessionState>
Hope this helps.
Greetings,
Chavdar
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center