There was also another runtime Exception being thrown - this time the
culprit was the iFrame for GWT History (the exception was thrown at
the point the iframe's document was being accessed)... it was unused
and removing it fixed the problem.
I find it hard to believe that no one else has seen
On Tue, Sep 20, 2011 at 4:20 AM, DaveC david.andrew.chap...@gmail.comwrote:
There was also another runtime Exception being thrown - this time the
culprit was the iFrame for GWT History (the exception was thrown at
the point the iframe's document was being accessed)... it was unused
and
I think its a mixed-mode content problem (HTTPS for app and HTTP for your
requested image). I can't see the issue in our app which uses HTTPS for both
the app and all resources (to avoid the mixed-mode warning of browsers).
-- J.
--
Thanks for the replies John Jens,
The app can run in http/https, the user can then configure the app to
consume various resources, for example rss feeds, web services - in
this instance the feed resources contained images which were then
loaded over http.
The issue was/is that IE throws a
