one possible workaround: send from your page samplexxx a heartbeat to
the top page (remember the time of the last heartbeat). then you can
check this value.
if this value is too long not updated, then the iframe have a
different content.
On 1 Sep., 22:29, Jayant [EMAIL PROTECTED] wrote:
Hello,
You could implement a backend proxy that fetches the html page, parses
the content to patch all link references to go back through the proxy
prior to sending the modified page to the browser. Since the browser
thinks the iFrame pages are loaded form the backend proxy (same domain
as the rest
