-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RP silently blocks remote content with Protonmail #850
Comments
Hi @Watilin, thank you for your detailed report. It would be great if you could post a screenshot of RPC's request log after reproducing step 7. Thank you. :) |
the request log is not documented yet, but you can see here how it works: #853 |
Hi! Sorry for the waiting. I’m bringing a full new report using Pale Moon, with a capture showing the request log as asked— in hope that this will shed some light on the situation. Browser and Add-ons
RequestPolicy settings:
Please note: steps to reproduce and results are exactly the same as before, I’m just copy-pasting for convenience. Steps to reproduce
What happens? No image appears in the email. The Request Policy icon does not turn red, and the menu does not mention anything blocked. What should happen? The menu should tell what content Request Policy has blocked, and offer a way to unblock it. The blocked image does appear in the request log. There be the screen capture :) |
Confirmed, see also #867. |
Browser and Add-ons
RequestPolicy settings:
Steps to reproduce
What happens?
No image appears in the email. The Request Policy icon does not turn red, and the menu does not mention anything blocked.
What should happen?
The menu should tell what content Request Policy has blocked, and offer a way to unblock it.
Another experiment makes it possible to be certain that Request Policy is what blocks the image once you click on Protonmail’s unblock button:
Now you should see the images.
Due to the encrypted nature of Protonmail, I’m not sure how Request Policy determines what is remote content; yet it manages to block it somehow.
The workaround I’m using is to allow any request from Protonmail.com, but this lacks fine-grain tuning.
The text was updated successfully, but these errors were encountered: