-
Notifications
You must be signed in to change notification settings - Fork 83
Invisible Requests? #112
Comments
I did try the above and it worked. But I have this recipe:
When you log into Google, I think there is a lot of redirections etc., so for the sake of simplicity, I think in the case of Google, whitelisting Google domain when on a page matching If you look into Statistics page, you might be able to track the key request which was blocked. |
Is there perhaps a way for HTTPSB to detect a redirect, and show the requests for the redirected page? The rule you provided could work. I'll use it. |
I would have to do some experiments, and if I find I can, I could report these redirects into the log in the Statistics page? |
That would be an improvement, though it would then require manual rules added by the user since it wouldn't be reflected by the matrix. |
Given the saga of the Window Resizer extension, whereas a user was deceived and tricked into having his requests redirected to a third-party web site, I really need to try to figure a way for the user to be informed when such thing happens. I am trying now to find a way to report the redirect into the matrix of the final landing page. The difficulty is to associate the redirect request to the landing page. This will require a journal to keep track of such redirect requests, and when a tab is finally bound to a landing page, there would need to be a reverse lookup for all redirects which occurred for that tab. Now to report this, I see only the |
Reporting in the There is a better way to report redirects which fits perfectly in the current model: in none of the column. A redirect can easily be seen as a top Top So redirects will be reported as top In the request log, using the above example, |
I have whitelisted every request for accounts.google.com , yet I still can not log into services until I turn HTTPSB off. Once I've logged in the issue doesn't persist. But when trying to go to a new google service it happens.
First time it happened I was trying to log into Google+, then again when trying to log into play.google.com.
The text was updated successfully, but these errors were encountered: