Open jsamuel opened 12 years ago
This also seems to affect any requests made by a page after it's finished loading, so AJAX-heavy pages, complicated redirects (i.e. Windows LIVE integration on sites), and pretty much any resource loaded by a page contained in an IFRAME -- these all tend to be missing from RP's UI.
From what I recall of the source, the GUI lists of (blocked?) cross-site requests are guessed from the source of the page (eg src attributes); however, other requests are also possible.
For example, a greasemonkey userscript to parse a page and redirect to another domain will silently fail. The cause turned out to be that this was considered a cross-site request and shouldLoad() blocked, but there was no GUI indication.
After manually adding the domain as an allowed cross-site request, all worked as expected. Nevertheless, this behavior is particularly counter-intuitive and the list of blocked requests is incomplete...